Removed versionadded/changed annotations for 1.9.

2 files changed, 0 insertions, 19 deletions

diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index eca477bdd9..4d6160c3fb 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -252,8 +252,6 @@ The initial serialization is usually very quick, but if you wish to exclude
 some apps from this process (and speed up test runs slightly), you may add
 those apps to :setting:`TEST_NON_SERIALIZED_APPS`.
 
-.. versionchanged:: 1.9
-
 To prevent serialized data from being loaded twice, setting
 ``serialized_rollback=True`` disables the
 :data:`~django.db.models.signals.post_migrate` signal when flushing the test
diff --git a/docs/topics/testing/tools.txt b/docs/topics/testing/tools.txt
index d2ef214c36..6663ccad8f 100644
--- a/docs/topics/testing/tools.txt
+++ b/docs/topics/testing/tools.txt
@@ -379,8 +379,6 @@ Use the ``django.test.Client`` class to make requests.
 
     .. method:: Client.force_login(user, backend=None)
 
-        .. versionadded:: 1.9
-
         If your site uses Django's :doc:`authentication
         system</topics/auth/index>`, you can use the ``force_login()`` method
         to simulate the effect of a user logging into the site. Use this method
@@ -461,8 +459,6 @@ Specifically, a ``Response`` object has the following attributes:
 
     .. method:: json(**kwargs)
 
-        .. versionadded:: 1.9
-
         The body of the response, parsed as JSON. Extra keyword arguments are
         passed to :func:`json.loads`. For example::
 
@@ -658,8 +654,6 @@ If your tests make any database queries, use subclasses
 
 .. attribute:: SimpleTestCase.allow_database_queries
 
-    .. versionadded:: 1.9
-
     :class:`~SimpleTestCase` disallows database queries by default. This
     helps to avoid executing write queries which will affect other tests
     since each ``SimpleTestCase`` test isn't run in a transaction. If you
@@ -824,11 +818,6 @@ By default the live server listens on ``localhost`` and picks the first
 available port in the ``8081-8179`` range. Its full URL can be accessed with
 ``self.live_server_url`` during the tests.
 
-.. versionchanged:: 1.9
-
-    In earlier versions, the live server's default address was always
-    ``'localhost:8081'``.
-
 If you'd like to select another address, you may pass a different one using the
 :option:`test --liveserver` option, for example:
 
@@ -836,12 +825,6 @@ If you'd like to select another address, you may pass a different one using the
 
     $ ./manage.py test --liveserver=localhost:8082
 
-.. versionchanged:: 1.9
-
-    In older versions ``live_server_url`` could only be accessed from an
-    instance. It now is a class property and can be accessed from class methods
-    like ``setUpClass()``.
-
 Another way of changing the default server address is by setting the
 `DJANGO_LIVE_TEST_SERVER_ADDRESS` environment variable somewhere in your
 code (for example, in a :ref:`custom test runner<topics-testing-test_runner>`)::