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/http/sessions.txt

@@ -29,8 +29,6 @@ from your ``INSTALLED_APPS``. It'll save you a small bit of overhead.
 Configuring the session engine
 ==============================
 
-.. versionadded:: 1.0
-
 By default, Django stores sessions in your database (using the model
 ``django.contrib.sessions.models.Session``). Though this is convenient, in
 some setups it's faster to store session data elsewhere, so Django can be
@@ -50,9 +48,6 @@ Using cached sessions
 
 For better performance, you may want to use a cache-based session backend.
 
-.. versionchanged:: 1.1
-   Django 1.0 did not include the ``cached_db`` session backend.
-
 To store session data using Django's cache system, you'll first need to make
 sure you've configured your cache; see the :doc:`cache documentation
 </topics/cache>` for details.
@@ -138,15 +133,10 @@ A session object has the following standard dictionary methods:
 
     * ``clear()``
 
-.. versionadded:: 1.0
-   ``setdefault()`` and ``clear()`` are new in this version.
-
 It also has these methods:
 
     * ``flush()``
 
-      .. versionadded:: 1.0
-
       Delete the current session data from the session and regenerate the
       session key value that is sent back to the user in the cookie. This is
       used if you want to ensure that the previous session data can't be
@@ -173,8 +163,6 @@ It also has these methods:
 
     * ``set_expiry(value)``
 
-      .. versionadded:: 1.0
-
       Sets the expiration time for the session. You can pass a number of
       different values:
 
@@ -198,24 +186,18 @@ It also has these methods:
 
     * ``get_expiry_age()``
 
-      .. versionadded:: 1.0
-
       Returns the number of seconds until this session expires. For sessions
       with no custom expiration (or those set to expire at browser close), this
       will equal ``settings.SESSION_COOKIE_AGE``.
 
     * ``get_expiry_date()``
 
-      .. versionadded:: 1.0
-
       Returns the date this session will expire. For sessions with no custom
       expiration (or those set to expire at browser close), this will equal the
       date ``settings.SESSION_COOKIE_AGE`` seconds from now.
 
     * ``get_expire_at_browser_close()``
 
-      .. versionadded:: 1.0
-
       Returns either ``True`` or ``False``, depending on whether the user's
       session cookie will expire when the user's Web browser is closed.
 
@@ -302,8 +284,6 @@ Here's a typical usage example::
 Using sessions out of views
 ===========================
 
-.. versionadded:: 1.0
-
 An API is available to manipulate session data outside of a view::
 
     >>> from django.contrib.sessions.backends.db import SessionStore
@@ -393,8 +373,6 @@ browser-length cookies -- cookies that expire as soon as the user closes his or
 her browser. Use this if you want people to have to log in every time they open
 a browser.
 
-.. versionadded:: 1.0
-
 This setting is a global default and can be overwritten at a per-session level
 by explicitly calling ``request.session.set_expiry()`` as described above in
 `using sessions in views`_.
@@ -424,11 +402,6 @@ A few :doc:`Django settings </ref/settings>` give you control over session behav
 SESSION_ENGINE
 --------------
 
-.. versionadded:: 1.0
-
-.. versionchanged:: 1.1
-   The ``cached_db`` backend was added
-
 Default: ``django.contrib.sessions.backends.db``
 
 Controls where Django stores session data. Valid values are:
@@ -443,8 +416,6 @@ See `configuring the session engine`_ for more details.
 SESSION_FILE_PATH
 -----------------
 
-.. versionadded:: 1.0
-
 Default: ``/tmp/``
 
 If you're using file-based session storage, this sets the directory in
@@ -493,8 +464,6 @@ The name of the cookie to use for sessions. This can be whatever you want.
 SESSION_COOKIE_PATH
 -------------------
 
-.. versionadded:: 1.0
-
 Default: ``'/'``
 
 The path set on the session cookie. This should either match the URL path of