Removed versionadded/changed annotations for 1.11.

7 files changed, 0 insertions, 74 deletions

diff --git a/docs/ref/models/database-functions.txt b/docs/ref/models/database-functions.txt
index f5a9af3a05..293dc4d91a 100644
--- a/docs/ref/models/database-functions.txt
+++ b/docs/ref/models/database-functions.txt
@@ -433,8 +433,6 @@ Usage example::
 
 .. class:: ExtractWeek(expression, tzinfo=None, **extra)
 
-    .. versionadded:: 1.11
-
     .. attribute:: lookup_name = 'week'
 
 .. class:: ExtractQuarter(expression, tzinfo=None, **extra)
@@ -698,8 +696,6 @@ that deal with date-parts can be used with ``DateField``::
 ``TimeField`` truncation
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.11
-
 .. class:: TruncHour(expression, output_field=None, tzinfo=None, **extra)
 
     .. attribute:: kind = 'hour'
@@ -764,8 +760,6 @@ truncate function. It's also registered as a transform on  ``DateTimeField`` as
 
 .. class:: TruncTime(expression, **extra)
 
-.. versionadded:: 1.11
-
     .. attribute:: lookup_name = 'time'
     .. attribute:: output_field = TimeField()
 
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt
index 6ef1001a9f..28cfb7c51b 100644
--- a/docs/ref/models/expressions.txt
+++ b/docs/ref/models/expressions.txt
@@ -463,8 +463,6 @@ expressions. For more details see :doc:`conditional-expressions`.
 
 .. class:: Subquery(queryset, output_field=None)
 
-.. versionadded:: 1.11
-
 You can add an explicit subquery to a ``QuerySet`` using the ``Subquery``
 expression.
 
@@ -498,8 +496,6 @@ Referencing columns from the outer queryset
 
 .. class:: OuterRef(field)
 
-.. versionadded:: 1.11
-
 Use ``OuterRef`` when a queryset in a ``Subquery`` needs to refer to a field
 from the outer query. It acts like an :class:`F` expression except that the
 check to see if it refers to a valid field isn't made until the outer queryset
@@ -549,8 +545,6 @@ row: the email address of the most recently created comment.
 
 .. class:: Exists(queryset)
 
-.. versionadded:: 1.11
-
 ``Exists`` is a ``Subquery`` subclass that uses an SQL ``EXISTS`` statement. In
 many cases it will perform better than a subquery since the database is able to
 stop evaluation of the subquery when a first matching row is found.
@@ -949,20 +943,12 @@ calling the appropriate methods on the wrapped expression.
 
         ``nulls_first`` and ``nulls_last`` define how null values are sorted.
 
-        .. versionchanged:: 1.11
-
-            The ``nulls_last`` and ``nulls_first`` parameters were added.
-
     .. method:: desc(nulls_first=False, nulls_last=False)
 
         Returns the expression ready to be sorted in descending order.
 
         ``nulls_first`` and ``nulls_last`` define how null values are sorted.
 
-        .. versionchanged:: 1.11
-
-            The ``nulls_first`` and ``nulls_last`` parameters were added.
-
     .. method:: reverse_ordering()
 
         Returns ``self`` with any modifications required to reverse the sort
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index aaa03cac0a..bcbda45145 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -315,10 +315,6 @@ This option is valid on all field types except :class:`ManyToManyField` and
 Note that when ``unique`` is ``True``, you don't need to specify
 :attr:`~Field.db_index`, because ``unique`` implies the creation of an index.
 
-.. versionchanged:: 1.11
-
-    In older versions, ``unique=True`` can't be used on :class:`FileField`.
-
 ``unique_for_date``
 -------------------
 
diff --git a/docs/ref/models/indexes.txt b/docs/ref/models/indexes.txt
index 6e8ab210ee..b751989e0c 100644
--- a/docs/ref/models/indexes.txt
+++ b/docs/ref/models/indexes.txt
@@ -6,8 +6,6 @@ Model index reference
 
 .. currentmodule:: django.db.models
 
-.. versionadded:: 1.11
-
 Index classes ease creating database indexes. They can be added using the
 :attr:`Meta.indexes <django.db.models.Options.indexes>` option. This document
 explains the API references of :class:`Index` which includes the `index
diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt
index 188552dbb2..fe51a1a362 100644
--- a/docs/ref/models/options.txt
+++ b/docs/ref/models/options.txt
@@ -387,8 +387,6 @@ Django quotes column and table names behind the scenes.
 
 .. attribute:: Options.indexes
 
-    .. versionadded:: 1.11
-
     A list of :doc:`indexes </ref/models/indexes>` that you want to define on
     the model::
 
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index f85ce1e441..ea2a3ef060 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -610,10 +610,6 @@ You can also refer to fields on related models with reverse relations through
    pronounced if you include multiple such fields in your ``values()`` query,
    in which case all possible combinations will be returned.
 
-.. versionchanged:: 1.11
-
-    Support for ``**expressions`` was added.
-
 ``values_list()``
 ~~~~~~~~~~~~~~~~~
 
@@ -684,10 +680,6 @@ not having any author::
     >>> Entry.objects.values_list('authors')
     <QuerySet [('Noam Chomsky',), ('George Orwell',), (None,)]>
 
-.. versionchanged:: 1.11
-
-    Support for expressions in ``*fields`` was added.
-
 .. versionchanged:: 2.0
 
     The ``named`` parameter was added.
@@ -809,8 +801,6 @@ query by calling ``all()`` on a previously evaluated ``QuerySet``.
 
 .. method:: union(*other_qs, all=False)
 
-.. versionadded:: 1.11
-
 Uses SQL's ``UNION`` operator to combine the results of two or more
 ``QuerySet``\s. For example:
 
@@ -831,17 +821,11 @@ slicing, :meth:`count`, and :meth:`order_by`) are allowed on the resulting
 allowed in the combined queries. For example, most databases don't allow
 ``LIMIT`` or ``OFFSET`` in the combined queries.
 
-.. versionchanged:: 1.11.4
-
-    ``COUNT(*)`` support was added.
-
 ``intersection()``
 ~~~~~~~~~~~~~~~~~~
 
 .. method:: intersection(*other_qs)
 
-.. versionadded:: 1.11
-
 Uses SQL's ``INTERSECT`` operator to return the shared elements of two or more
 ``QuerySet``\s. For example:
 
@@ -854,8 +838,6 @@ See :meth:`union` for some restrictions.
 
 .. method:: difference(*other_qs)
 
-.. versionadded:: 1.11
-
 Uses SQL's ``EXCEPT`` operator to keep only elements present in the
 ``QuerySet`` but not in some other ``QuerySet``\s. For example::
 
@@ -1077,10 +1059,6 @@ database.
     :class:`related managers<django.db.models.fields.related.RelatedManager>`,
     any prefetched cache for the relation will be cleared.
 
-    .. versionchanged:: 1.11
-
-        The clearing of the prefetched cache described above was added.
-
 You can also use the normal join syntax to do related fields of related
 fields. Suppose we have an additional model to the example above::
 
@@ -1686,10 +1664,6 @@ raised if ``select_for_update()`` is used in autocommit mode.
     PostgreSQL doesn't support ``select_for_update()`` with
     :class:`~django.db.models.expressions.Window` expressions.
 
-.. versionchanged:: 1.11
-
-    The ``skip_locked`` argument was added.
-
 .. versionchanged:: 2.0
 
     The ``of`` argument was added.
@@ -1895,10 +1869,6 @@ whenever a request to a page has a side effect on your data. For more, see
   chapter because it isn't related to that book, but it can't create it either
   because ``title`` field should be unique.
 
-.. versionchanged:: 1.11
-
-    Added support for callable values in ``defaults``.
-
 ``update_or_create()``
 ~~~~~~~~~~~~~~~~~~~~~~
 
@@ -1945,10 +1915,6 @@ As described above in :meth:`get_or_create`, this method is prone to a
 race-condition which can result in multiple rows being inserted simultaneously
 if uniqueness is not enforced at the database level.
 
-.. versionchanged:: 1.11
-
-    Added support for callable values in ``defaults``.
-
 ``bulk_create()``
 ~~~~~~~~~~~~~~~~~
 
@@ -2097,10 +2063,6 @@ psycopg mailing list <https://www.postgresql.org/message-id/4D2F2C71.8080805%40d
     between the number of rows transferred and the data discarded if the loop
     is exited early.
 
-.. versionchanged:: 1.11
-
-    PostgreSQL support for server-side cursors was added.
-
 .. versionchanged:: 2.0
 
     The ``chunk_size`` parameter was added.
@@ -2831,8 +2793,6 @@ in the database <database-time-zone-definitions>`.
 ``week``
 ~~~~~~~~
 
-.. versionadded:: 1.11
-
 For date and datetime fields, return the week number (1-52 or 53) according
 to `ISO-8601 <https://en.wikipedia.org/wiki/ISO-8601>`_, i.e., weeks start
 on a Monday and the first week starts on or before Thursday.
@@ -2902,8 +2862,6 @@ in the database <database-time-zone-definitions>`.
 ``time``
 ~~~~~~~~
 
-.. versionadded:: 1.11
-
 For datetime fields, casts the value as time. Allows chaining additional field
 lookups. Takes a :class:`datetime.time` value.
 
diff --git a/docs/ref/models/relations.txt b/docs/ref/models/relations.txt
index 9cb61d14ed..beffe1283e 100644
--- a/docs/ref/models/relations.txt
+++ b/docs/ref/models/relations.txt
@@ -173,7 +173,3 @@ Related objects reference
        If you use :meth:`~django.db.models.query.QuerySet.prefetch_related`,
        the ``add()``, ``remove()``, ``clear()``, and ``set()`` methods clear
        the prefetched cache.
-
-       .. versionchanged:: 1.11
-
-            The clearing of the prefetched cache described above was added.