Fixed #14000 - remove versionadded/changed tags for Django 1.0 and 1.1

git-svn-id: http://code.djangoproject.com/svn/django/trunk@15055 bcc190cf-cafb-0310-a4f2-bffc1f526a37

docs/topics/db/aggregation.txt

@@ -2,8 +2,6 @@
 Aggregation
 ===========
 
-.. versionadded:: 1.1
-
 .. currentmodule:: django.db.models
 
 The topic guide on :doc:`Django's database-abstraction API </topics/db/queries>`

docs/topics/db/models.txt

@@ -387,8 +387,6 @@ work; all are optional.
 Extra fields on many-to-many relationships
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.0
-
 When you're only dealing with simple many-to-many relationships such as
 mixing and matching pizzas and toppings, a standard :class:`~django.db.models.ManyToManyField` is all you need. However, sometimes
 you may need to associate data with the relationship between two models.
@@ -553,8 +551,6 @@ can be made; see :ref:`the model field reference <ref-onetoone>` for details.
 
 .. _One-to-one relationship model example: http://www.djangoproject.com/documentation/models/one_to_one/
 
-.. versionadded:: 1.0
-
 :class:`~django.db.models.OneToOneField` fields also accept one optional argument
 described in the :ref:`model field reference <ref-onetoone>`.
 
@@ -606,8 +602,6 @@ particular database engine.
 Custom field types
 ------------------
 
-.. versionadded:: 1.0
-
 If one of the existing model fields cannot be used to fit your purposes, or if
 you wish to take advantage of some less common database column types, you can
 create your own field class. Full coverage of creating your own fields is
@@ -769,8 +763,6 @@ on :doc:`using raw SQL</topics/db/sql>`.
 Model inheritance
 =================
 
-.. versionadded:: 1.0
-
 Model inheritance in Django works almost identically to the way normal
 class inheritance works in Python. The only decision you have to make
 is whether you want the parent models to be models in their own right
@@ -1026,8 +1018,6 @@ to indicate that your field is the link back to the parent class.
 Proxy models
 ------------
 
-.. versionadded:: 1.1
-
 When using :ref:`multi-table inheritance <multi-table-inheritance>`, a new
 database table is created for each subclass of a model. This is usually the
 desired behavior, since the subclass needs a place to store any additional

docs/topics/db/queries.txt

@@ -475,8 +475,6 @@ those latter objects, you could write::
 Spanning multi-valued relationships
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.0
-
 When you are filtering an object based on a ``ManyToManyField`` or a reverse
 ``ForeignKey``, there are two different sorts of filter you may be
 interested in. Consider the ``Blog``/``Entry`` relationship (``Blog`` to
@@ -532,8 +530,6 @@ filtering on different linked objects.
 Filters can reference fields on the model
 -----------------------------------------
 
-.. versionadded:: 1.1
-
 In the examples given so far, we have constructed filters that compare
 the value of a model field with a constant. But what if you want to compare
 the value of a model field with another field on the same model?
@@ -818,8 +814,6 @@ complete query set::
 Updating multiple objects at once
 =================================
 
-.. versionadded:: 1.0
-
 Sometimes you want to set a field to a particular value for all the objects in
 a ``QuerySet``. You can do this with the ``update()`` method. For example::
 
@@ -858,8 +852,6 @@ Just loop over them and call ``save()``::
     for item in my_queryset:
         item.save()
 
-.. versionadded:: 1.1
-
 Calls to update can also use :ref:`F() objects <query-expressions>` to update
 one field based on the value of another field in the model. This is especially
 useful for incrementing counters based upon their current value. For example, to

docs/topics/db/transactions.txt

@@ -338,8 +338,6 @@ In this example, ``a.save()`` will not be undone in the case where
 Database-level autocommit
 -------------------------
 
-.. versionadded:: 1.1
-
 With PostgreSQL 8.2 or later, there is an advanced option to run PostgreSQL
 with :doc:`database-level autocommit </ref/databases>`. If you use this option,
 there is no constantly open transaction, so it is always possible to continue