Removing several "2.1" references, which is consistent with our release process:

"Remove all versionadded directives - and any other notes related to features changing or being new - for the version (e.g. 2.1) from the master branch. The result is that the next release (which is the first that comes entirely after the end of maintenance of this branch), will have no mentions of the old version (e.g. 2.1)."

This should have been done when 2.1 reached end of maintenance, but the release process wasn't formed at that time.

Also, the release of 2.3 and the end of maintenance for 2.1 were unique because they basically happened at the same time. For our purposes, we assume that 2.3 was released before the 2.1 end of life, which means that the 2.1 references are removed for 2.4 (master), not for 2.3.

Author: weaverryan

book/forms.rst

@@ -1792,11 +1792,6 @@ The answer is to setup the constraints yourself, and attach them to the individu
 fields. The overall approach is covered a bit more in the :ref:`validation chapter<book-validation-raw-values>`,
 but here's a short example:
 
-.. versionadded:: 2.1
-   The ``constraints`` option, which accepts a single constraint or an array
-   of constraints (before 2.1, the option was called ``validation_constraint``,
-   and only accepted a single constraint) is new to Symfony 2.1.
-
 .. code-block:: php
 
     use Symfony\Component\Validator\Constraints\Length;

book/security.rst

@@ -418,12 +418,8 @@ submission (i.e.  ``/login_check``):
 
     You will *not* need to implement a controller for the ``/login_check``
     URL as the firewall will automatically catch and process any form submitted
-    to this URL.
-
-.. versionadded:: 2.1
-    As of Symfony 2.1, you *must* have routes configured for your ``login_path``,
-    ``check_path`` ``logout`` keys. These keys can be route names (as shown
-    in this example) or URLs that have routes configured for them.
+    to this URL. However, you *must* have a route (as shown here) for this
+    URL, as well as one for your logout path (see :ref:`book-security-logging-out`).
 
 Notice that the name of the ``login`` route matches the ``login_path`` config
 value, as that's where the security system will redirect users that need
@@ -1700,6 +1696,8 @@ In the above configuration, users with ``ROLE_ADMIN`` role will also have the
 ``ROLE_USER`` role. The ``ROLE_SUPER_ADMIN`` role has ``ROLE_ADMIN``, ``ROLE_ALLOWED_TO_SWITCH``
 and ``ROLE_USER`` (inherited from ``ROLE_ADMIN``).
 
+.. _book-security-logging-out:
+
 Logging Out
 -----------
 

book/translation.rst

@@ -557,11 +557,6 @@ by defining a ``default_locale`` for the framework:
             'default_locale' => 'en',
         ));
 
-.. versionadded:: 2.1
-     The ``default_locale`` parameter was defined under the session key
-     originally, however, as of 2.1 this has been moved. This is because the
-     locale is now set on the request instead of the session.
-
 .. _book-translation-locale-url:
 
 The Locale and the URL

components/config/definition.rst

@@ -100,8 +100,8 @@ node definition. Node type are available for:
 * scalar
 * boolean
 * integer (new in 2.2)
-* float (new in 2.2)
-* enum (new in 2.1)
+* float
+* enum
 * array
 * variable (no validation)
 
@@ -136,9 +136,6 @@ allowing to validate the value::
 Enum nodes
 ~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The enum node is new in Symfony 2.1
-
 Enum nodes provide a constraint to match the given input against a set of
 values::
 

components/event_dispatcher/immutable_dispatcher.rst

@@ -4,9 +4,6 @@
 The Immutable Event Dispatcher
 ==============================
 
-.. versionadded:: 2.1
-    This feature was added in Symfony 2.1.
-
 The :class:`Symfony\\Component\\EventDispatcher\\ImmutableEventDispatcher` is
 a locked or frozen event dispatcher. The dispatcher cannot register new
 listeners or subscribers.

components/process.rst

@@ -64,9 +64,6 @@ anonymous function to the
         }
     });
 
-.. versionadded:: 2.1
-    The non-blocking feature was added in 2.1.
-
 Running Processes Asynchronously
 --------------------------------
 

cookbook/configuration/pdo_session_storage.rst

@@ -14,13 +14,6 @@ Symfony2 has a built-in solution for database session storage called
 To use it, you just need to change some parameters in ``config.yml`` (or the
 configuration format of your choice):
 
-.. versionadded:: 2.1
-    In Symfony2.1 the class and namespace are slightly modified. You can now
-    find the session storage classes in the `Session\\Storage` namespace:
-    ``Symfony\Component\HttpFoundation\Session\Storage``. Also
-    note that in Symfony2.1 you should configure ``handler_id`` not ``storage_id`` like in Symfony2.0.
-    Below, you'll notice that ``%session.storage.options%`` is not used anymore.
-
 .. configuration-block::
 
     .. code-block:: yaml

reference/constraints/Regex.rst

@@ -177,9 +177,6 @@ string *does* match this pattern.
 htmlPattern
 ~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The ``htmlPattern`` option was added in Symfony 2.1
-
 **type**: ``string|Boolean`` **default**: null
 
 This option specifies the pattern to use in the HTML5 ``pattern`` attribute.

reference/dic_tags.rst

@@ -964,9 +964,6 @@ translation.extractor
 
 **Purpose**: To register a custom service that extracts messages from a file
 
-.. versionadded:: 2.1
-   The ability to add message extractors is new in Symfony 2.1.
-
 When executing the ``translation:update`` command, it uses extractors to
 extract translation messages from a file. By default, the Symfony2 framework
 has a :class:`Symfony\\Bridge\\Twig\\Translation\\TwigExtractor` and a
@@ -1035,9 +1032,6 @@ translation.dumper
 
 **Purpose**: To register a custom service that dumps messages to a file
 
-.. versionadded:: 2.1
-   The ability to add message dumpers is new in Symfony 2.1.
-
 After an `Extractor <translation.extractor>`_ has extracted all messages from
 the templates, the dumpers are executed to dump the messages to a translation
 file in a specific format.