Removed versionadded/changed notes for 1.7.

2 files changed, 2 insertions, 26 deletions

diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
index 9faca5b9e1..b98d4128ad 100644
--- a/docs/ref/templates/api.txt
+++ b/docs/ref/templates/api.txt
@@ -442,8 +442,6 @@ If you ``pop()`` too much, it'll raise
     ...
     ContextPopException
 
-.. versionadded:: 1.7
-
 You can also use ``push()`` as a context manager to ensure a matching ``pop()``
 is called.
 
@@ -490,8 +488,6 @@ tags <howto-writing-custom-template-tags>`.
 
 .. method:: Context.flatten()
 
-.. versionadded:: 1.7
-
 Using ``flatten()`` method you can get whole ``Context`` stack as one dictionary
 including builtin variables.
 
@@ -705,10 +701,6 @@ variables:
 * ``DEFAULT_MESSAGE_LEVELS`` -- A mapping of the message level names to
   :ref:`their numeric value <message-level-constants>`.
 
-.. versionchanged:: 1.7
-
-       The ``DEFAULT_MESSAGE_LEVELS`` variable was added.
-
 Writing your own context processors
 -----------------------------------
 
@@ -941,8 +933,6 @@ the template source, and returns a tuple: ``(template, template_origin)``.
 Template origin
 ===============
 
-.. versionadded:: 1.7
-
 When an :class:`~django.template.Engine` is initialized with ``debug=True``,
 its templates have an ``origin`` attribute depending on the source they are
 loaded from. For engines initialized by Django, ``debug`` defaults to the
diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt
index b9d2afb603..da1ec04ab3 100644
--- a/docs/ref/templates/builtins.txt
+++ b/docs/ref/templates/builtins.txt
@@ -665,11 +665,8 @@ the variable ``template_name``::
 
     {% include template_name %}
 
-.. versionchanged:: 1.7
-
-    The variable may also be any object with a ``render()`` method that
-    accepts a context. This allows you to reference a compiled ``Template`` in
-    your context.
+The variable may also be any object with a ``render()`` method that accepts a
+context. This allows you to reference a compiled ``Template`` in your context.
 
 An included template is rendered within the context of the template that
 includes it. This example produces the output ``"Hello, John"``:
@@ -1177,10 +1174,6 @@ variable. It can be useful, for instance, in a :ttag:`blocktrans` like this::
     {% widthratio this_value max_value max_width as width %}
     {% blocktrans %}The width is: {{ width }}{% endblocktrans %}
 
-.. versionchanged:: 1.7
-
-    The ability to use "as" with this tag like in the example above was added.
-
 .. templatetag:: with
 
 with
@@ -2153,11 +2146,6 @@ When used without a format string::
 ...the formatting string defined in the :setting:`TIME_FORMAT` setting will be
 used, without applying any localization.
 
-.. versionchanged:: 1.7
-
-    The ability to receive and act on values with attached timezone
-    information was added in Django 1.7.
-
 .. templatefilter:: timesince
 
 timesince
@@ -2235,8 +2223,6 @@ If ``value`` is ``"Joel is a slug"``, the output will be ``"Joel i..."``.
 truncatechars_html
 ^^^^^^^^^^^^^^^^^^
 
-.. versionadded:: 1.7
-
 Similar to :tfilter:`truncatechars`, except that it is aware of HTML tags. Any
 tags that are opened in the string and not closed before the truncation point
 are closed immediately after the truncation.