Fixed #18934 - Removed versionadded/changed annotations for Django 1.3

docs/topics/http/middleware.txt

@@ -117,8 +117,6 @@ middleware is always called on every response.
 ``process_template_response``
 -----------------------------
 
-.. versionadded:: 1.3
-
 .. method:: process_template_response(self, request, response)
 
 ``request`` is an :class:`~django.http.HttpRequest` object. ``response`` is a

docs/topics/http/shortcuts.txt

@@ -17,8 +17,6 @@ introduce controlled coupling for convenience's sake.
 
 .. function:: render(request, template_name[, dictionary][, context_instance][, content_type][, status][, current_app])
 
-   .. versionadded:: 1.3
-
    Combines a given template with a given context dictionary and returns an
    :class:`~django.http.HttpResponse` object with that rendered text.
 

docs/topics/http/urls.txt

@@ -980,13 +980,6 @@ A :class:`ResolverMatch` object can also be assigned to a triple::
 
     func, args, kwargs = resolve('/some/path/')
 
-.. versionchanged:: 1.3
-    Triple-assignment exists for backwards-compatibility. Prior to
-    Django 1.3, :func:`~django.core.urlresolvers.resolve` returned a
-    triple containing (view function, arguments, keyword arguments);
-    the :class:`ResolverMatch` object (as well as the namespace and pattern
-    information it provides) is not available in earlier Django releases.
-
 One possible use of :func:`~django.core.urlresolvers.resolve` would be to test
 whether a view would raise a ``Http404`` error before redirecting to it::