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/ref/contrib/admin/actions.txt

@@ -2,8 +2,6 @@
 Admin actions
 =============
 
-.. versionadded:: 1.1
-
 .. currentmodule:: django.contrib.admin
 
 The basic workflow of Django's admin is, in a nutshell, "select an object,

docs/ref/contrib/admin/index.txt

@@ -434,8 +434,6 @@ subclass::
 
 .. attribute:: ModelAdmin.list_editable
 
-    .. versionadded:: 1.1
-
     Set ``list_editable`` to a list of field names on the model which will
     allow editing on the change list page. That is, fields listed in
     ``list_editable`` will be displayed as form widgets on the change list
@@ -678,8 +676,6 @@ subclass::
 
 .. attribute:: ModelAdmin.formfield_overrides
 
-    .. versionadded:: 1.1
-
     This provides a quick-and-dirty way to override some of the
     :class:`~django.forms.Field` options for use in the admin.
     ``formfield_overrides`` is a dictionary mapping a field class to a dict of
@@ -722,16 +718,12 @@ subclass::
 
 .. attribute:: ModelAdmin.actions
 
-    .. versionadded:: 1.1
-
     A list of actions to make available on the change list page. See
     :doc:`/ref/contrib/admin/actions` for details.
 
 .. attribute:: ModelAdmin.actions_on_top
 .. attribute:: ModelAdmin.actions_on_bottom
 
-    .. versionadded:: 1.1
-
     Controls where on the page the actions bar appears. By default, the admin
     changelist displays actions at the top of the page (``actions_on_top = True;
     actions_on_bottom = False``).
@@ -843,8 +835,6 @@ templates used by the :class:`ModelAdmin` views:
 
 .. method:: ModelAdmin.get_urls(self)
 
-    .. versionadded:: 1.1
-
     The ``get_urls`` method on a ``ModelAdmin`` returns the URLs to be used for
     that ModelAdmin in the same way as a URLconf.  Therefore you can extend
     them as documented in :doc:`/topics/http/urls`::
@@ -903,8 +893,6 @@ templates used by the :class:`ModelAdmin` views:
 
 .. method:: ModelAdmin.formfield_for_foreignkey(self, db_field, request, **kwargs)
 
-    .. versionadded:: 1.1
-
     The ``formfield_for_foreignkey`` method on a ``ModelAdmin`` allows you to
     override the default formfield for a foreign key field. For example, to
     return a subset of objects for this foreign key field based on the user::
@@ -920,8 +908,6 @@ templates used by the :class:`ModelAdmin` views:
 
 .. method:: ModelAdmin.formfield_for_manytomany(self, db_field, request, **kwargs)
 
-    .. versionadded:: 1.1
-
     Like the ``formfield_for_foreignkey`` method, the
     ``formfield_for_manytomany`` method can be overridden to change the
     default formfield for a many to many field. For example, if an owner can
@@ -1119,9 +1105,6 @@ adds some of its own (the shared features are actually defined in the
 - :attr:`~ModelAdmin.prepopulated_fields`
 - :attr:`~ModelAdmin.radio_fields`
 - :attr:`~InlineModelAdmin.raw_id_fields`
-
-.. versionadded:: 1.1
-
 - :meth:`~ModelAdmin.formfield_for_foreignkey`
 - :meth:`~ModelAdmin.formfield_for_manytomany`
 
@@ -1512,8 +1495,6 @@ creating your own ``AdminSite`` instance (see below), and changing the
     Python class), and register your models and ``ModelAdmin`` subclasses
     with it instead of using the default.
 
-    .. versionadded:: 1.1
-
     When constructing an instance of an ``AdminSite``, you are able to provide
     a unique instance name using the ``name`` argument to the constructor. This
     instance name is used to identify the instance, especially when
@@ -1607,10 +1588,6 @@ It's easy to create multiple instances of the admin site on the same
 Django-powered Web site. Just create multiple instances of ``AdminSite`` and
 root each one at a different URL.
 
-.. versionchanged:: 1.1
-    The method for hooking ``AdminSite`` instances into urls has changed in
-    Django 1.1.
-
 In this example, the URLs ``/basic-admin/`` and ``/advanced-admin/`` feature
 separate versions of the admin site -- using the ``AdminSite`` instances
 ``myproject.admin.basic_site`` and ``myproject.admin.advanced_site``,
@@ -1633,8 +1610,6 @@ is only necessary if you are using more than one ``AdminSite``.
 Adding views to admin sites
 ---------------------------
 
-.. versionadded:: 1.1
-
 Just like :class:`ModelAdmin`, :class:`AdminSite` provides a
 :meth:`~django.contrib.admin.ModelAdmin.get_urls()` method
 that can be overridden to define additional views for the site. To add
@@ -1654,8 +1629,6 @@ a pattern for your new view.
 Reversing Admin URLs
 ====================
 
-.. versionadded:: 1.1
-
 When an :class:`AdminSite` is deployed, the views provided by that site are
 accessible using Django's :ref:`URL reversing system <naming-url-patterns>`.