From 5446b72003790fc98bd926f7196b26cc5db63c5a Mon Sep 17 00:00:00 2001
From: Tim Graham <timograham@gmail.com>
Date: Sat, 2 Sep 2017 21:49:07 -0400
Subject: Removed versionadded/changed annotations for 1.11.

---
 docs/ref/forms/api.txt       | 9 ---------
 docs/ref/forms/fields.txt    | 2 --
 docs/ref/forms/renderers.txt | 5 -----
 docs/ref/forms/widgets.txt   | 2 --
 4 files changed, 18 deletions(-)

(limited to 'docs/ref/forms')

diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt
index e68222f977..5e001a2f62 100644
--- a/docs/ref/forms/api.txt
+++ b/docs/ref/forms/api.txt
@@ -261,8 +261,6 @@ precedence::
 
 .. method:: Form.get_initial_for_field(field, field_name)
 
-.. versionadded:: 1.11
-
 Use :meth:`~Form.get_initial_for_field()` to retrieve initial data for a form
 field. It retrieves data from :attr:`Form.initial` and :attr:`Field.initial`,
 in that order, and evaluates any callable initial values.
@@ -462,11 +460,6 @@ include ``checked`` if appropriate::
     <tr><th><label for="id_sender">Sender:</label></th><td><input type="email" name="sender" id="id_sender" value="foo@example.com" required /></td></tr>
     <tr><th><label for="id_cc_myself">Cc myself:</label></th><td><input type="checkbox" name="cc_myself" id="id_cc_myself" checked /></td></tr>
 
-.. versionchanged:: 1.11
-
-    The ``checked`` attribute was changed to use HTML5 boolean syntax rather
-    than ``checked="checked"``.
-
 This default output is a two-column HTML table, with a ``<tr>`` for each field.
 Notice the following:
 
@@ -734,8 +727,6 @@ Configuring the rendering of a form's widgets
 
 .. attribute:: Form.default_renderer
 
-.. versionadded:: 1.11
-
 Specifies the :doc:`renderer <renderers>` to use for the form. Defaults to
 ``None`` which means to use the default renderer specified by the
 :setting:`FORM_RENDERER` setting.
diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt
index ca889771d1..7c28c0e7e1 100644
--- a/docs/ref/forms/fields.txt
+++ b/docs/ref/forms/fields.txt
@@ -386,8 +386,6 @@ For each field, we describe the default widget used if you don't specify
 
     .. attribute:: empty_value
 
-       .. versionadded:: 1.11
-
        The value to use to represent "empty". Defaults to an empty string.
 
 ``ChoiceField``
diff --git a/docs/ref/forms/renderers.txt b/docs/ref/forms/renderers.txt
index fcf025a9c8..68669221fb 100644
--- a/docs/ref/forms/renderers.txt
+++ b/docs/ref/forms/renderers.txt
@@ -5,11 +5,6 @@ The form rendering API
 .. module:: django.forms.renderers
    :synopsis: Built-in form renderers.
 
-.. versionadded:: 1.11
-
-    In older versions, widgets are rendered using Python. All APIs described
-    in this document are new.
-
 Django's form widgets are rendered using Django's :doc:`template engines
 system </topics/templates>`.
 
diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt
index 9fad3c69f5..7e43e3d354 100644
--- a/docs/ref/forms/widgets.txt
+++ b/docs/ref/forms/widgets.txt
@@ -238,8 +238,6 @@ foundation for custom widgets.
 
     .. method:: get_context(name, value, attrs)
 
-        .. versionadded:: 1.11
-
         Returns a dictionary of values to use when rendering the widget
         template. By default, the dictionary contains a single key,
         ``'widget'``, which is a dictionary representation of the widget
-- 
cgit v1.3