Removed 2.x versionadded directives

Author: wouterj

book/forms.rst

@@ -122,10 +122,6 @@ other things, determines which HTML form tag(s) is rendered for that field.
 Finally, you added a submit button with a custom label for submitting the form to
 the server.
 
-.. versionadded:: 2.3
-    Support for submit buttons was introduced in Symfony 2.3. Before that, you had
-    to add buttons to the form's HTML manually.
-
 Symfony comes with many built-in types that will be discussed shortly
 (see :ref:`book-forms-type-reference`).
 
@@ -240,12 +236,6 @@ controller::
         // ...
     }
 
-.. versionadded:: 2.3
-    The :method:`Symfony\\Component\\Form\\FormInterface::handleRequest` method
-    was introduced in Symfony 2.3. Previously, the ``$request`` was passed
-    to the ``submit`` method - a strategy which is deprecated and will be
-    removed in Symfony 3.0. For details on that method, see :ref:`cookbook-form-submit-request`.
-
 This controller follows a common pattern for handling forms, and has three
 possible paths:
 
@@ -294,9 +284,6 @@ possible paths:
 Submitting Forms with Multiple Buttons
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    Support for buttons in forms was introduced in Symfony 2.3.
-
 When your form contains more than one submit button, you will want to check
 which of the buttons was clicked to adapt the program flow in your controller.
 To do this, add a second button with the caption "Save and add" to your form::
@@ -492,9 +479,6 @@ be used to validate the underlying object.
 Disabling Validation
 ~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    The ability to set ``validation_groups`` to false was introduced in Symfony 2.3.
-
 Sometimes it is useful to suppress the validation of a form altogether. For
 these cases you can set the ``validation_groups`` option to ``false``::
 
@@ -593,9 +577,6 @@ work in the book section about :ref:`validation groups <book-validation-validati
 Groups based on the Clicked Button
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    Support for buttons in forms was introduced in Symfony 2.3.
-
 When your form contains multiple submit buttons, you can change the validation
 group depending on which button is used to submit the form. For example,
 consider a form in a wizard that lets you advance to the next step or go back
@@ -1872,11 +1853,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) was introduced in Symfony 2.1.
-
 .. code-block:: php
 
     use Symfony\Component\Validator\Constraints\Length;

book/routing.rst

@@ -87,10 +87,6 @@ The route is simple:
 
         return $collection;
 
-.. versionadded:: 2.2
-    The ``path`` option was introduced in Symfony 2.2, ``pattern`` is used
-    in older versions.
-
 The path defined by the ``blog_show`` route acts like ``/blog/*`` where
 the wildcard is given the name ``slug``. For the URL ``/blog/my-blog-post``,
 the ``slug`` variable gets a value of ``my-blog-post``, which is available
@@ -891,10 +887,6 @@ be accomplished with the following route configuration:
 
         return $collection;
 
-.. versionadded:: 2.2
-    The ``methods`` option was introduced in Symfony 2.2. Use the ``_method``
-    requirement in older versions.
-
 Despite the fact that these two routes have identical paths (``/contact``),
 the first route will match only GET requests and the second route will match
 only POST requests. This means that you can display the form and submit the
@@ -907,9 +899,6 @@ form via the same URL, while using distinct controllers for the two actions.
 Adding a Host Requirement
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    Host matching support was introduced in Symfony 2.2
-
 You can also match on the HTTP *host* of the incoming request. For more
 information, see :doc:`/components/routing/hostname_pattern` in the Routing
 component documentation.
@@ -1289,9 +1278,6 @@ be prefixed with the string ``/site``.
 Adding a Host Requirement to Imported Routes
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    Host matching support was introduced in Symfony 2.2
-
 You can set the host regex on imported routes. For more information, see
 :ref:`component-routing-host-imported`.
 

book/templating.rst

@@ -377,11 +377,6 @@ When working with template inheritance, here are some tips to keep in mind:
 Template Naming and Locations
 -----------------------------
 
-.. versionadded:: 2.2
-    Namespaced path support was introduced in 2.2, allowing for template names
-    like ``@AcmeDemo/layout.html.twig``. See :doc:`/cookbook/templating/namespaced_paths`
-    for more details.
-
 By default, templates can live in two different locations:
 
 ``app/Resources/views/``
@@ -582,10 +577,6 @@ you set `with_context`_ to false).
     maps (i.e. an array with named keys). If you needed to pass in multiple
     elements, it would look like this: ``{'foo': foo, 'bar': bar}``.
 
-.. versionadded:: 2.2
-    The `include() function`_ is a new Twig feature that's available in Symfony
-    2.2. Prior, the `{% include %} tag`_ tag was used.
-
 .. index::
    single: Templating; Embedding action
 
@@ -691,9 +682,6 @@ that as much code as possible lives in reusable :doc:`services </book/service_co
 Asynchronous Content with hinclude.js
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    hinclude.js support was introduced 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),
 Symfony uses a version of the standard ``render`` function to configure ``hinclude``
@@ -801,9 +789,6 @@ in your application configuration:
             ),
         ));
 
-.. versionadded:: 2.2
-    Default templates per render function was introduced in Symfony 2.2
-
 You can define default templates per ``render`` function (which will override
 any global default template that is defined):
 

book/testing.rst

@@ -407,11 +407,6 @@ The Client supports many operations that can be done in a real browser::
 Accessing internal Objects
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    The :method:`Symfony\\Component\\BrowserKit\\Client::getInternalRequest`
-    and :method:`Symfony\\Component\\BrowserKit\\Client::getInternalResponse`
-    methods were introduced in Symfony 2.3.
-
 If you use the client to test your application, you might want to access the
 client's internal objects::
 

book/translation.rst

@@ -307,9 +307,6 @@ texts* and complex expressions:
     Note that this only influences the current template, not any "included"
     template (in order to avoid side effects).
 
-.. versionadded:: 2.1
-    The ``trans_default_domain`` tag was introduced in Symfony 2.1.
-
 PHP Templates
 ~~~~~~~~~~~~~
 
@@ -537,11 +534,6 @@ 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-constraint-messages:
 
 Translating Constraint Messages

components/class_loader/cache_class_loader.rst

@@ -26,9 +26,6 @@ for a class.
 ApcClassLoader
 --------------
 
-.. versionadded:: 2.1
-    The ``ApcClassLoader`` class was introduced in Symfony 2.1.
-
 ``ApcClassLoader`` wraps an existing class loader and caches calls to its
 ``findFile()`` method using `APC`_::
 
@@ -49,9 +46,6 @@ ApcClassLoader
 XcacheClassLoader
 -----------------
 
-.. versionadded:: 2.1
-    The ``XcacheClassLoader`` class was introduced in Symfony 2.1.
-
 ``XcacheClassLoader`` uses `XCache`_ to cache a class loader. Registering
 it is straightforward::
 

components/class_loader/class_loader.rst

@@ -4,9 +4,6 @@
 The PSR-0 Class Loader
 ======================
 
-.. versionadded:: 2.1
-    The ``ClassLoader`` class was introduced in Symfony 2.1.
-
 If your classes and third-party libraries follow the `PSR-0`_ standard, you
 can use the :class:`Symfony\\Component\\ClassLoader\\ClassLoader` class to
 load all of your project's classes.

components/class_loader/debug_class_loader.rst

@@ -4,9 +4,6 @@
 Debugging a Class Loader
 ========================
 
-.. versionadded:: 2.1
-    The ``DebugClassLoader`` class was introduced in Symfony 2.1.
-
 The :class:`Symfony\\Component\\ClassLoader\\DebugClassLoader` attempts to
 throw more helpful exceptions when a class isn't found by the registered
 autoloaders. All autoloaders that implement a ``findFile()`` method are replaced

components/config/definition.rst

@@ -111,9 +111,6 @@ and are created with ``node($name, $type)`` or their associated shortcut
 Numeric Node Constraints
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    The numeric (float and integer) nodes were introduced in Symfony 2.2.
-
 Numeric nodes (float and integer) provide two extra constraints -
 :method:`Symfony\\Component\\Config\\Definition\\Builder::min` and
 :method:`Symfony\\Component\\Config\\Definition\\Builder::max` -
@@ -136,9 +133,6 @@ allowing to validate the value::
 Enum Nodes
 ~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The enum node was introduced in Symfony 2.1.
-
 Enum nodes provide a constraint to match the given input against a set of
 values::
 
@@ -299,10 +293,6 @@ The info will be printed as a comment when dumping the configuration tree.
 Optional Sections
 -----------------
 
-.. versionadded:: 2.2
-    The ``canBeEnabled`` and ``canBeDisabled`` methods were introduced in
-    Symfony 2.2.
-
 If you have entire sections which are optional and can be enabled/disabled,
 you can take advantage of the shortcut
 :method:`Symfony\\Component\\Config\\Definition\\Builder\\ArrayNodeDefinition::canBeEnabled` and

components/console/events.rst

@@ -4,9 +4,6 @@
 Using Events
 ============
 
-.. versionadded:: 2.3
-    Console events were introduced in Symfony 2.3.
-
 The Application class of the Console component allows you to optionally hook
 into the lifecycle of a console application via events. Instead of reinventing
 the wheel, it uses the Symfony EventDispatcher component to do the work::

components/console/helpers/dialoghelper.rst

@@ -59,9 +59,6 @@ If they leave it empty, the default value (``AcmeDemoBundle`` here) is returned.
 Autocompletion
 ~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    Autocompletion for questions was introduced in Symfony 2.2.
-
 You can also specify an array of potential answers for a given question. These
 will be autocompleted as the user types::
 
@@ -77,9 +74,6 @@ will be autocompleted as the user types::
 Hiding the User's Response
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    The ``askHiddenResponse`` method was introduced in Symfony 2.2.
-
 You can also ask a question and hide the response. This is particularly
 convenient for passwords::
 
@@ -149,9 +143,6 @@ be able to proceed if their input is valid.
 Validating a Hidden Response
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    The ``askHiddenResponseAndValidate`` method was introduced in Symfony 2.2.
-
 You can also ask and validate a hidden response::
 
     $dialog = $this->getHelper('dialog');
@@ -178,10 +169,6 @@ some reason, pass true as the fifth argument.
 Let the User Choose from a List of Answers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.2
-    The :method:`Symfony\\Component\\Console\\Helper\\DialogHelper::select` method
-    was introduced in Symfony 2.2.
-
 If you have a predefined set of answers the user can choose from, you
 could use the ``ask`` method described above or, to make sure the user
 provided a correct answer, the ``askAndValidate`` method. Both have
@@ -214,9 +201,6 @@ or the maximum attempts is reached (which you can define in the fifth
 argument). The default value for the attempts is ``false``, which means infinite
 attempts. You can define your own error message in the sixth argument.
 
-.. versionadded:: 2.3
-    Multiselect support was introduced in Symfony 2.3.
-
 Multiple Choices
 ................
 

components/console/helpers/progresshelper.rst

@@ -4,12 +4,6 @@
 Progress Helper
 ===============
 
-.. versionadded:: 2.2
-    The ``progress`` helper was introduced in Symfony 2.2.
-
-.. versionadded:: 2.3
-    The ``setCurrent`` method was introduced in Symfony 2.3.
-
 When executing longer-running commands, it may be helpful to show progress
 information, which updates as your command runs:
 

components/console/helpers/tablehelper.rst

@@ -4,9 +4,6 @@
 Table Helper
 ============
 
-.. versionadded:: 2.3
-    The ``table`` helper was introduced in Symfony 2.3.
-
 When building a console application it may be useful to display tabular data:
 
 .. image:: /images/components/console/table.png

components/console/introduction.rst

@@ -168,10 +168,6 @@ You can also set these colors and options inside the tagname::
 Verbosity Levels
 ~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-   The ``VERBOSITY_VERY_VERBOSE`` and ``VERBOSITY_DEBUG`` constants were introduced
-   in version 2.3
-
 The console has 5 levels of verbosity. These are defined in the
 :class:`Symfony\\Component\\Console\\Output\\OutputInterface`:
 

components/debug.rst

@@ -7,10 +7,6 @@ The Debug Component
 
     The Debug component provides tools to ease debugging PHP code.
 
-.. versionadded:: 2.3
-    The Debug component was introduced in Symfony 2.3. Previously, the classes
-    were located in the HttpKernel component.
-
 Installation
 ------------
 

components/dependency_injection/compilation.rst

@@ -277,10 +277,6 @@ but also load a secondary one only if a certain parameter is set::
 Prepending Configuration Passed to the Extension
 ------------------------------------------------
 
-.. versionadded:: 2.2
-    The ability to prepend the configuration of a bundle was introduced in
-    Symfony 2.2.
-
 An Extension can prepend the configuration of any Bundle before the ``load()``
 method is called by implementing :class:`Symfony\\Component\\DependencyInjection\\Extension\\PrependExtensionInterface`::
 

components/dependency_injection/lazy_services.rst

@@ -4,9 +4,6 @@
 Lazy Services
 =============
 
-.. versionadded:: 2.3
-   Lazy services were introduced in Symfony 2.3.
-
 Why lazy Services?
 ------------------
 

components/dom_crawler.rst

@@ -159,11 +159,6 @@ Call an anonymous function on each node of the list::
         return $node->text();
     });
 
-.. versionadded:: 2.3
-    As seen here, in Symfony 2.3, the ``each`` and ``reduce`` Closure functions
-    are passed a ``Crawler`` as the first argument. Previously, that argument
-    was a :phpclass:`DOMNode`.
-
 The anonymous function receives the node (as a Crawler) and the position as arguments.
 The result is an array of values returned by the anonymous function calls.