Remove old versionadded and versionchanged

Removed versionadded and versionchanged for version prior to 1.2 since they
are no longer useful.

Change-Id: I5c53d1188bc5fec3ab4be39ef761650ed8fa6d3e

9 files changed, 0 insertions, 54 deletions

diff --git a/doc/build/core/connections.rst b/doc/build/core/connections.rst
index 726b5a501..dc81750cd 100644
--- a/doc/build/core/connections.rst
+++ b/doc/build/core/connections.rst
@@ -855,9 +855,6 @@ as the schema name is passed to these methods explicitly.
     configurations, the :ref:`horizontal_sharding_toplevel` extension may
     be used.  See the example at :ref:`examples_sharding`.
 
-
-.. versionadded:: 1.1
-
 .. _sql_caching:
 
 
diff --git a/doc/build/core/constraints.rst b/doc/build/core/constraints.rst
index 3b05b8c12..1efccdce5 100644
--- a/doc/build/core/constraints.rst
+++ b/doc/build/core/constraints.rst
@@ -259,18 +259,6 @@ like the following is generated:
     sqlalchemy.exc.CompileError: Can't emit DROP CONSTRAINT for constraint
     ForeignKeyConstraint(...); it has no name
 
-.. versionchanged:: 1.0.0 - The DDL system invoked by
-   :meth:`_schema.MetaData.create_all`
-   and :meth:`_schema.MetaData.drop_all` will now automatically resolve mutually
-   dependent foreign keys between tables declared by
-   :class:`_schema.ForeignKeyConstraint` and :class:`_schema.ForeignKey` objects, without
-   the need to explicitly set the :paramref:`_schema.ForeignKeyConstraint.use_alter`
-   flag.
-
-.. versionchanged:: 1.0.0 - The :paramref:`_schema.ForeignKeyConstraint.use_alter`
-   flag can be used with an un-named constraint; only the DROP operation
-   will emit a specific error when actually called upon.
-
 .. seealso::
 
     :ref:`constraint_naming_conventions`
@@ -730,9 +718,6 @@ one column present, the scan does use a deterministic search, however the
 structure of the expression will determine which column is noted as
 "column zero".
 
-.. versionadded:: 1.0.0 The :class:`.CheckConstraint` object now supports
-   the ``column_0_name`` naming convention token.
-
 .. _naming_schematypes:
 
 Configuring Naming for Boolean, Enum, and other schema types
@@ -790,9 +775,6 @@ The above schema will produce:
         CONSTRAINT ck_foo_flag CHECK (flag IN (0, 1))
     )
 
-.. versionchanged:: 1.0 Constraint naming conventions that don't include
-   ``%(constraint_name)s`` again work with :class:`.SchemaType` constraints.
-
 Constraints API
 ---------------
 
diff --git a/doc/build/core/event.rst b/doc/build/core/event.rst
index 3347b1336..427da8fb1 100644
--- a/doc/build/core/event.rst
+++ b/doc/build/core/event.rst
@@ -81,9 +81,6 @@ as long as the names match up::
 Above, the presence of ``**kw`` tells :func:`.listens_for` that
 arguments should be passed to the function by name, rather than positionally.
 
-.. versionadded:: 0.9.0 Added optional ``named`` argument dispatch to
-   event calling.
-
 Targets
 -------
 
diff --git a/doc/build/orm/declarative_config.rst b/doc/build/orm/declarative_config.rst
index 71acefe52..873f16aff 100644
--- a/doc/build/orm/declarative_config.rst
+++ b/doc/build/orm/declarative_config.rst
@@ -338,9 +338,6 @@ configuration via the :meth:`.MapperEvents.before_configured` event::
             """ """
             # do something before mappings are configured
 
-.. versionadded:: 0.9.3
-
-
 .. _declarative_metadata:
 
 ``metadata``
diff --git a/doc/build/orm/join_conditions.rst b/doc/build/orm/join_conditions.rst
index f89565445..79c3e98ad 100644
--- a/doc/build/orm/join_conditions.rst
+++ b/doc/build/orm/join_conditions.rst
@@ -483,11 +483,6 @@ annotating with :func:`_orm.foreign`::
             "Writer.magazine_id == Article.magazine_id)",
         )
 
-.. versionchanged:: 1.0.0 the ORM will attempt to warn when a column is used
-   as the synchronization target from more than one relationship
-   simultaneously.
-
-
 Non-relational Comparisons / Materialized Path
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -527,11 +522,6 @@ we seek for a load of ``Element.descendants`` to look like:
     FROM element
     WHERE element.path LIKE ('/foo/bar2' || '/%') ORDER BY element.path
 
-.. versionadded:: 0.9.5 Support has been added to allow a single-column
-   comparison to itself within a primaryjoin condition, as well as for
-   primaryjoin conditions that use :meth:`.ColumnOperators.like` as the comparison
-   operator.
-
 .. _self_referential_many_to_many:
 
 Self-Referential Many-to-Many Relationship
diff --git a/doc/build/orm/persistence_techniques.rst b/doc/build/orm/persistence_techniques.rst
index 0a68befb3..dca6cefff 100644
--- a/doc/build/orm/persistence_techniques.rst
+++ b/doc/build/orm/persistence_techniques.rst
@@ -243,9 +243,6 @@ value and pass it through, rather than omitting it as a "missing" value::
   signal to the ORM that we'd like ``None`` to be passed into the type whenever
   present, even though no special type-level behaviors are assigned to it.
 
-.. versionadded:: 1.1 added the :meth:`.TypeEngine.evaluates_none` method
-   in order to indicate that a "None" value should be treated as significant.
-
 .. _orm_server_defaults:
 
 Fetching Server-Generated Defaults
diff --git a/doc/build/orm/session_events.rst b/doc/build/orm/session_events.rst
index 6223b53f6..f61421ea9 100644
--- a/doc/build/orm/session_events.rst
+++ b/doc/build/orm/session_events.rst
@@ -410,9 +410,6 @@ Object Lifecycle Events
 Another use case for events is to track the lifecycle of objects.  This
 refers to the states first introduced at :ref:`session_object_states`.
 
-.. versionadded:: 1.1 added a system of events that intercept all possible
-   state transitions of an object within the :class:`.Session`.
-
 All the states above can be tracked fully with events.   Each event
 represents a distinct state transition, meaning, the starting state
 and the destination state are both part of what are tracked.   With the
diff --git a/doc/build/orm/session_state_management.rst b/doc/build/orm/session_state_management.rst
index 26a51cfb2..3538bdc22 100644
--- a/doc/build/orm/session_state_management.rst
+++ b/doc/build/orm/session_state_management.rst
@@ -30,9 +30,6 @@ It's helpful to know the states which an instance can have within a session:
   the session's transaction is rolled back, a deleted object moves
   *back* to the persistent state.
 
-  .. versionchanged:: 1.1 The 'deleted' state is a newly added session
-     object state distinct from the 'persistent' state.
-
 * **Detached** - an instance which corresponds, or previously corresponded,
   to a record in the database, but is not currently in any session.
   The detached object will contain a database identity marker, however
diff --git a/doc/build/orm/versioning.rst b/doc/build/orm/versioning.rst
index abbe14937..87865917c 100644
--- a/doc/build/orm/versioning.rst
+++ b/doc/build/orm/versioning.rst
@@ -209,9 +209,6 @@ It is *strongly recommended* that server side version counters only be used
 when absolutely necessary and only on backends that support :term:`RETURNING`,
 currently PostgreSQL, Oracle, MariaDB 10.5, SQLite 3.35, and SQL Server.
 
-.. versionadded:: 0.9.0
-
-    Support for server side version identifier tracking.
 
 Programmatic or Conditional Version Counters
 --------------------------------------------
@@ -255,8 +252,3 @@ issues::
     # will leave version_uuid unchanged
     u1.name = "u3"
     session.commit()
-
-.. versionadded:: 0.9.0
-
-    Support for programmatic and conditional version identifier tracking.
-