Removed versionadded/changed annotations dating back to 1.4.

docs/howto/custom-template-tags.txt

@@ -333,8 +333,6 @@ Template filter code falls into one of two situations:
 Filters and time zones
 ~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.4
-
 If you write a custom filter that operates on :class:`~datetime.datetime`
 objects, you'll usually register it with the ``expects_localtime`` flag set to
 ``True``:
@@ -764,8 +762,6 @@ Or, using decorator syntax:
 For more information on how the ``takes_context`` option works, see the section
 on :ref:`inclusion tags<howto-custom-template-tags-inclusion-tags>`.
 
-.. versionadded:: 1.4
-
 If you need to rename your tag, you can provide a custom name for it:
 
 .. code-block:: python
@@ -776,8 +772,6 @@ If you need to rename your tag, you can provide a custom name for it:
     def some_function(value):
         return value - 2
 
-.. versionadded:: 1.4
-
 ``simple_tag`` functions may accept any number of positional or keyword
 arguments. For example:
 
@@ -865,16 +859,14 @@ template loader, we'd register the tag like this:
     # Here, register is a django.template.Library instance, as before
     register.inclusion_tag('results.html')(show_results)
 
-.. versionchanged:: 1.4
+Alternatively it is possible to register the inclusion tag using a
+:class:`django.template.Template` instance:
 
-    Alternatively it is possible to register the inclusion tag using a
-    :class:`django.template.Template` instance:
+.. code-block:: python
 
-    .. code-block:: python
-
-        from django.template.loader import get_template
-        t = get_template('results.html')
-        register.inclusion_tag(t)(show_results)
+    from django.template.loader import get_template
+    t = get_template('results.html')
+    register.inclusion_tag(t)(show_results)
 
 As always, decorator syntax works as well, so we could have written:
 
@@ -932,8 +924,6 @@ The ``takes_context`` parameter defaults to ``False``. When it's set to
 ``True``, the tag is passed the context object, as in this example. That's the
 only difference between this case and the previous ``inclusion_tag`` example.
 
-.. versionadded:: 1.4
-
 ``inclusion_tag`` functions may accept any number of positional or keyword
 arguments. For example:
 
@@ -1046,8 +1036,6 @@ context-updating template tag, you might want to consider using an
 Assignment tags
 ~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.4
-
 To ease the creation of tags setting a variable in the context, Django provides
 a helper function, ``assignment_tag``. This function works the same way as
 :ref:`simple_tag<howto-custom-template-tags-simple-tags>`, except that it

docs/howto/deployment/wsgi/index.txt

@@ -28,8 +28,6 @@ callable object which the webserver uses to communicate with your code. This is
 commonly specified as an object named ``application`` in a Python module
 accessible to the server.
 
-.. versionchanged:: 1.4
-
 The :djadmin:`startproject` command creates a :file:`projectname/wsgi.py` that
 contains such an application callable.
 

docs/howto/error-reporting.txt

@@ -106,8 +106,6 @@ The best way to disable this behavior is to set
 Filtering error reports
 -----------------------
 
-.. versionadded:: 1.4
-
 Filtering sensitive information
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -185,15 +183,11 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``):
         def my_view(request):
             ...
 
-.. note::
-
-    .. versionchanged:: 1.4
-
-    Since version 1.4, all POST parameters are systematically filtered out of
-    error reports for certain :mod:`django.contrib.auth.views` views (
-    ``login``, ``password_reset_confirm``, ``password_change``, and
-    ``add_view`` and ``user_change_password`` in the ``auth`` admin) to prevent
-    the leaking of sensitive information such as user passwords.
+    All POST parameters are systematically filtered out of error reports for
+    certain :mod:`django.contrib.auth.views` views (``login``,
+    ``password_reset_confirm``, ``password_change``, and ``add_view`` and
+    ``user_change_password`` in the ``auth`` admin) to prevent the leaking of
+    sensitive information such as user passwords.
 
 .. _custom-error-reports: