Removed versionadded:: 2.1 directives

Author: wouterj

book/forms.rst

@@ -183,9 +183,6 @@ it into a format that's suitable for being rendered in an HTML form.
    (e.g. ``isPublished()`` or ``hasReminder()``) instead of a getter (e.g.
    ``getPublished()`` or ``getReminder()``).
 
-   .. versionadded:: 2.1
-        Support for "hasser" methods was added in Symfony 2.1.
-
 .. index::
   single: Forms; Handling form submission
 
@@ -408,10 +405,6 @@ be used to validate the underlying object.
 Groups based on Submitted Data
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-   The ability to specify a callback or Closure in ``validation_groups``
-   is new to version 2.1
-
 If you need some advanced logic to determine the validation groups (e.g.
 based on submitted data), you can set the ``validation_groups`` option
 to an array callback, or a ``Closure``::
@@ -1235,18 +1228,13 @@ To customize any portion of a form, you just need to override the appropriate
 fragment. Knowing exactly which block or file to override is the subject of
 the next section.
 
-.. versionadded:: 2.1
-   An alternate Twig syntax for ``form_theme`` has been introduced in 2.1. It accepts
-   any valid Twig expression (the most noticeable difference is using an array when
-   using multiple themes).
-
-   .. code-block:: html+jinja
+.. code-block:: html+jinja
 
-       {# src/Acme/TaskBundle/Resources/views/Default/new.html.twig #}
+    {# src/Acme/TaskBundle/Resources/views/Default/new.html.twig #}
 
-       {% form_theme form with 'AcmeTaskBundle:Form:fields.html.twig' %}
+    {% form_theme form with 'AcmeTaskBundle:Form:fields.html.twig' %}
 
-       {% form_theme form with ['AcmeTaskBundle:Form:fields.html.twig', 'AcmeTaskBundle:Form:fields2.html.twig'] %}
+    {% form_theme form with ['AcmeTaskBundle:Form:fields.html.twig', 'AcmeTaskBundle:Form:fields2.html.twig'] %}
 
 For a more extensive discussion, see :doc:`/cookbook/form/form_customization`.
 
@@ -1604,11 +1592,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/page_creation.rst

@@ -813,9 +813,6 @@ options of each feature.
 Default Configuration Dump
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The ``config:dump-reference`` command was added in Symfony 2.1
-
 You can dump the default configuration for a bundle in yaml to the console using
 the ``config:dump-reference`` command.  Here is an example of dumping the default
 FrameworkBundle configuration:

book/security.rst

@@ -410,11 +410,6 @@ submission (i.e.  ``/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.
-
 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
 to login.
@@ -1161,12 +1156,6 @@ custom user class is that it implements the :class:`Symfony\\Component\\Security
 interface. This means that your concept of a "user" can be anything, as long
 as it implements this interface.
 
-.. versionadded:: 2.1
-    In Symfony 2.1, the ``equals`` method was removed from ``UserInterface``.
-    If you need to override the default implementation of comparison logic,
-    implement the new :class:`Symfony\\Component\\Security\\Core\\User\\EquatableInterface`
-    interface.
-
 .. note::
 
     The user object will be serialized and saved in the session during requests,

book/service_container.rst

@@ -227,10 +227,6 @@ The end result is exactly the same as before - the difference is only in
 to look for parameters with those names. When the container is built, it
 looks up the value of each parameter and uses it in the service definition.
 
-.. versionadded:: 2.1
-    Escaping the ``@`` character in YAML parameter values is new in Symfony 2.1.9
-    and Symfony 2.2.1.
-
 .. note::
 
     If you want to use a string that starts with an ``@`` sign as a parameter

book/templating.rst

@@ -665,9 +665,6 @@ Controllers are fast to execute and promote good code organization and reuse.
 Asynchronous Content with hinclude.js
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    hinclude.js support was added in Symfony 2.1
-
 Controllers can be embedded asynchronously using the hinclude.js_ javascript library.
 As the embedded content comes from another page (or controller for that matter),
 Symfony2 uses the standard ``render`` helper to configure ``hinclude`` tags:
@@ -1443,9 +1440,6 @@ is ``true``. By default this means that the variables will be dumped in the
 Syntax Checking
 ---------------
 
-.. versionadded:: 2.1
-    The ``twig:lint`` command was added in Symfony 2.1
-
 You can check for syntax errors in Twig templates using the ``twig:lint``
 console command:
 

book/translation.rst

@@ -554,11 +554,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
@@ -825,9 +820,6 @@ texts* and complex expressions:
     Note that this only influences the current template, not any "included"
     templates (in order to avoid side effects).
 
-.. versionadded:: 2.1
-    The ``trans_default_domain`` tag is new in Symfony2.1
-
 PHP Templates
 ~~~~~~~~~~~~~
 

components/class_loader.rst

@@ -33,9 +33,6 @@ You can install the component in many different ways:
 Usage
 -----
 
-.. versionadded:: 2.1
-   The ``useIncludePath`` method was added in Symfony 2.1.
-
 Registering the :class:`Symfony\\Component\\ClassLoader\\UniversalClassLoader`
 autoloader is straightforward::
 

components/event_dispatcher/container_aware_dispatcher.rst

@@ -4,9 +4,6 @@
 The Container Aware Event Dispatcher
 ====================================
 
-.. versionadded:: 2.1
-    This feature was moved into the EventDispatcher component in Symfony 2.1.
-
 Introduction
 ------------
 

components/event_dispatcher/generic_event.rst

@@ -4,9 +4,6 @@
 The Generic Event Object
 ========================
 
-.. versionadded:: 2.1
-    The ``GenericEvent`` event class was added in Symfony 2.1
-
 The base :class:`Symfony\\Component\\EventDispatcher\\Event` class provided by the
 ``Event Dispatcher`` component is deliberately sparse to allow the creation of
 API specific event objects by inheritance using OOP. This allow for elegant and

components/event_dispatcher/introduction.rst

@@ -440,9 +440,6 @@ which returns a boolean value::
 EventDispatcher aware Events and Listeners
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The ``Event`` object contains a reference to the invoking dispatcher since Symfony 2.1
-
 The ``EventDispatcher`` always injects a reference to itself in the passed event
 object.  This means that all listeners have direct access to the
 ``EventDispatcher`` object that notified the listener via the passed ``Event``
@@ -535,9 +532,6 @@ can be the way to go, especially for optional dependencies.
 Dispatcher Shortcuts
 ~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    ``EventDispatcher::dispatch()`` method returns the event since Symfony 2.1.
-
 The :method:`EventDispatcher::dispatch<Symfony\\Component\\EventDispatcher\\EventDispatcher::dispatch>`
 method always returns an :class:`Symfony\\Component\\EventDispatcher\\Event`
 object. This allows for various shortcuts. For example if one does not need
@@ -575,9 +569,6 @@ and so on...
 Event Name Introspection
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    Added event name to the ``Event`` object since Symfony 2.1
-
 Since the ``EventDispatcher`` already knows the name of the event when dispatching
 it, the event name is also injected into the
 :class:`Symfony\\Component\\EventDispatcher\\Event` objects, making it available