[1.2.X] Fixed #14000 - Remove versionadded/changed tags for 1.0. thanks ramiro!

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@15056 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 0 insertions, 22 deletions

diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt
index 155f758040..665bddd756 100644
--- a/docs/topics/testing.txt
+++ b/docs/topics/testing.txt
@@ -256,9 +256,6 @@ with this command::
 
 Note that we used ``animals``, not ``myproject.animals``.
 
-.. versionadded:: 1.0
-   You can now choose which test to run.
-
 You can be even *more* specific by naming an individual test case. To
 run a single test case in an application (for example, the
 ``AnimalTestCase`` described in the "Writing unit tests" section), add
@@ -361,8 +358,6 @@ database is created by the user specified by ``USER``, so you'll need
 to make sure that the given user account has sufficient privileges to
 create a new database on the system.
 
-.. versionadded:: 1.0
-
 For fine-grained control over the character encoding of your test
 database, use the :setting:`TEST_CHARSET` option. If you're using
 MySQL, you can also use the :setting:`TEST_COLLATION` option to
@@ -836,8 +831,6 @@ arguments at time of construction:
 
     .. method:: Client.login(**credentials)
 
-        .. versionadded:: 1.0
-
         If your site uses Django's :doc:`authentication system</topics/auth>`
         and you deal with logging in users, you can use the test client's
         ``login()`` method to simulate the effect of a user logging into the
@@ -882,8 +875,6 @@ arguments at time of construction:
 
     .. method:: Client.logout()
 
-        .. versionadded:: 1.0
-
         If your site uses Django's :doc:`authentication system</topics/auth>`,
         the ``logout()`` method can be used to simulate the effect of a user
         logging out of your site.
@@ -1095,8 +1086,6 @@ by truncating tables and reloading initial data.
 Default test client
 ~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.0
-
 .. attribute:: TestCase.client
 
 Every test case in a ``django.test.TestCase`` instance has access to an
@@ -1201,8 +1190,6 @@ or by the order of test execution.
 URLconf configuration
 ~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.0
-
 .. attribute:: TestCase.urls
 
 If your application provides views, you may want to include tests that use the
@@ -1270,8 +1257,6 @@ This test case will flush *all* the test databases before running
 Emptying the test outbox
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.0
-
 If you use Django's custom ``TestCase`` class, the test runner will clear the
 contents of the test e-mail outbox at the start of each test case.
 
@@ -1280,8 +1265,6 @@ For more detail on e-mail services during tests, see `E-mail services`_.
 Assertions
 ~~~~~~~~~~
 
-.. versionadded:: 1.0
-
 .. versionchanged:: 1.2
     Addded ``msg_prefix`` argument.
 
@@ -1351,8 +1334,6 @@ cause of an failure in your test suite.
 E-mail services
 ---------------
 
-.. versionadded:: 1.0
-
 If any of your Django views send e-mail using :doc:`Django's e-mail
 functionality </topics/email>`, you probably don't want to send e-mail each time
 you run a test using that view. For this reason, Django's test runner
@@ -1601,9 +1582,6 @@ also provides some utilities that can be useful during testing.
     :setting:`NAME` in :setting:`DATABASES` to match the name of the test
     database.
 
-    .. versionchanged:: 1.0
-       ``create_test_db()`` now returns the name of the test database.
-
 .. function:: destroy_test_db(old_database_name, verbosity=1)
 
     Destroys the database whose name is in stored in :setting:`NAME` in the