Removed all 2.x versionadded directives

Author: wouterj

book/forms.rst

@@ -123,20 +123,9 @@ You've also assigned each a "type" (e.g. ``TextType`` and ``DateType``),
 represented by its fully qualified class name. Among other things, it determines
 which HTML form tag(s) is rendered for that field.
 
-.. versionadded:: 2.8
-    To denote the form type, you have to use the fully qualified class name - like
-    ``TextType::class`` in PHP 5.5+ or ``Symfony\Component\Form\Extension\Core\Type\TextType``.
-    Before Symfony 2.8, you could use an alias for each type like ``text`` or
-    ``date``. The old alias syntax will still work until Symfony 3.0. For more details,
-    see the `2.8 UPGRADE Log`_.
-
 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`).
 
@@ -259,12 +248,6 @@ your controller::
     is called. Otherwise, changes done in the ``*_SUBMIT`` events aren't applied to the
     view (like validation errors).
 
-.. 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:
 
@@ -313,9 +296,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::
@@ -491,10 +471,6 @@ you'll need to specify which validation group(s) your form should use::
         'validation_groups' => array('registration'),
     ))->add(...);
 
-.. versionadded:: 2.7
-    The ``configureOptions()`` method was introduced in Symfony 2.7. Previously,
-    the method was called ``setDefaultOptions()``.
-
 If you're creating :ref:`form classes <book-form-creating-form-classes>` (a
 good practice), then you'll need to add the following to the ``configureOptions()``
 method::
@@ -517,9 +493,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``::
 
@@ -620,9 +593,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

book/routing.rst

@@ -1543,10 +1543,6 @@ a template helper function:
             Read this blog post.
         </a>
 
-.. versionadded:: 2.8
-    The ``path()`` PHP templating helper was introduced in Symfony 2.8. Prior
-    to 2.8, you had to use the ``generate()`` helper method.
-
 .. index::
    single: Routing; Absolute URLs
 
@@ -1581,12 +1577,6 @@ URL) rather than the ``path()`` function (which generates a relative URL):
             Read this blog post.
         </a>
 
-.. versionadded:: 2.8
-    The ``url()`` PHP templating helper was introduced in Symfony 2.8. Prior
-    to 2.8, you had to use the ``generate()`` helper method with
-    ``Symfony\Component\Routing\Generator\UrlGeneratorInterface::ABSOLUTE_URL``
-    passed as the third argument.
-
 .. note::
 
     The host that's used when generating an absolute URL is automatically

book/templating.rst

@@ -579,10 +579,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.3
-    The `include() function`_ is available since Symfony 2.3. Prior, the
-    `{% include %} tag`_ was used.
-
 .. index::
    single: Templating; Embedding action
 

book/testing.rst

@@ -420,11 +420,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/validation.rst

@@ -103,11 +103,6 @@ following:
     Protected and private properties can also be validated, as well as "getter"
     methods (see :ref:`validator-constraint-targets`).
 
-.. versionadded:: 2.7
-    As of Symfony 2.7, XML and Yaml constraint files located in the
-    ``Resources/config/validation`` sub-directory of a bundle are loaded. Prior
-    to 2.7, only ``Resources/config/validation.yml`` (or ``.xml``) were loaded.
-
 .. index::
    single: Validation; Using the validator
 

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

@@ -208,9 +208,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,9 +4,6 @@
 Progress Helper
 ===============
 
-.. versionadded:: 2.3
-    The ``setCurrent`` method was introduced in Symfony 2.3.
-
 .. caution::
 
     The Progress Helper was deprecated in Symfony 2.5 and will be removed in

components/console/helpers/table.rst

@@ -147,9 +147,6 @@ Here is a full list of things you can customize:
 Spanning Multiple Columns and Rows
 ----------------------------------
 
-.. versionadded:: 2.7
-    Spanning multiple columns and rows was introduced in Symfony 2.7.
-
 To make a table cell that spans multiple columns you can use a :class:`Symfony\\Component\\Console\\Helper\\TableCell`::
 
     use Symfony\Component\Console\Helper\Table;

components/console/helpers/tablehelper.rst

@@ -4,9 +4,6 @@
 Table Helper
 ============
 
-.. versionadded:: 2.3
-    The ``table`` helper was introduced in Symfony 2.3.
-
 .. caution::
 
     The Table Helper was deprecated in Symfony 2.5 and will be removed in

components/console/introduction.rst

@@ -200,10 +200,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 five verbosity levels. These are defined in the
 :class:`Symfony\\Component\\Console\\Output\\OutputInterface`:
 

components/css_selector.rst

@@ -46,10 +46,6 @@ document.
 The CssSelector Component
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.8
-    The ``CssSelectorConverter`` class was introduced in Symfony 2.8. Previously,
-    the ``CssSelector`` class was used and ``toXPath`` was a static method.
-
 The component's only goal is to convert CSS selectors to their XPath
 equivalents, using :method:`Symfony\\Component\\CssSelector\\CssSelectorConverter::toXPath`::
 

components/debug/introduction.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/advanced.rst

@@ -219,11 +219,6 @@ You can change the inner service name if you want to:
             ->setPublic(false)
             ->setDecoratedService('foo', 'bar.wooz');
 
-.. versionadded:: 2.8
-    The ability to define the decoration priority was introduced in Symfony 2.8.
-    Prior to Symfony 2.8, the priority depends on the order in
-    which definitions are found.
-
 If you want to apply more than one decorator to a service, you can control their
 order by configuring the priority of decoration, this can be any integer number
 (decorators with higher priorities will be applied first).
@@ -295,9 +290,6 @@ The generated code will be the following:
 Deprecating Services
 --------------------
 
-.. versionadded:: 2.8
-    The ``deprecated`` setting was introduced in Symfony 2.8.
-
 Once you have decided to deprecate the use of a service (because it is outdated
 or you decided not to maintain it anymore), you can deprecate its definition:
 

components/dependency_injection/compilation.rst

@@ -331,11 +331,6 @@ compilation::
         // ...
     }
 
-.. versionadded:: 2.8
-    Prior to Symfony 2.8, extensions implementing ``CompilerPassInterface``
-    were not automatically registered. You needed to register them as explained
-    in :ref:`the next section <components-di-separate-compiler-passes>`.
-
 As ``process()`` is called *after* all extensions are loaded, it allows you to
 edit service definitions of other extensions as well as retrieving information
 about service definitions.

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

@@ -223,11 +223,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.
 

components/filesystem/introduction.rst

@@ -239,9 +239,6 @@ isAbsolutePath
 dumpFile
 ~~~~~~~~
 
-.. versionadded:: 2.3
-    The ``dumpFile()`` was introduced in Symfony 2.3.
-
 :method:`Symfony\\Component\\Filesystem\\Filesystem::dumpFile` allows you to
 dump contents to a file. It does this in an atomic manner: it writes a temporary
 file first and then moves it to the new file location when it's finished.

components/finder.rst

@@ -95,10 +95,6 @@ Exclude directories from matching with the
 
     $finder->in(__DIR__)->exclude('ruby');
 
-.. versionadded:: 2.3
-   The :method:`Symfony\\Component\\Finder\\Finder::ignoreUnreadableDirs`
-   method was introduced in Symfony 2.3.
-
 It's also possible to ignore directories that you don't have permission to read::
 
     $finder->ignoreUnreadableDirs()->in(__DIR__);

components/form/form_events.rst

@@ -257,11 +257,6 @@ Name                    ``FormEvents`` Constant        Event's Data
 ``form.post_bind``      ``FormEvents::POST_SUBMIT``    View data
 ======================  =============================  ===============
 
-.. versionadded:: 2.3
-    Before Symfony 2.3, ``FormEvents::PRE_SUBMIT``, ``FormEvents::SUBMIT``
-    and ``FormEvents::POST_SUBMIT`` were called ``FormEvents::PRE_BIND``,
-    ``FormEvents::BIND`` and ``FormEvents::POST_BIND``.
-
 .. caution::
 
     The ``FormEvents::PRE_BIND``, ``FormEvents::BIND`` and

components/form/introduction.rst

@@ -68,9 +68,6 @@ factory.
 Request Handling
 ~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    The ``handleRequest()`` method was introduced in Symfony 2.3.
-
 To process form data, you'll need to call the :method:`Symfony\\Component\\Form\\Form::handleRequest`
 method::
 
@@ -519,10 +516,6 @@ to do that in the ":ref:`form-rendering-template`" section.
 Changing a Form's Method and Action
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.3
-    The ability to configure the form method and action was introduced in
-    Symfony 2.3.
-
 By default, a form is submitted to the same URI that rendered the form with
 an HTTP POST request. This behavior can be changed using the :ref:`form-option-action`
 and :ref:`form-option-method` options (the ``method`` option is also used

components/http_foundation/trusting_proxies.rst

@@ -19,10 +19,6 @@ Since HTTP headers can be spoofed, Symfony does *not* trust these proxy
 headers by default. If you are behind a proxy, you should manually whitelist
 your proxy.
 
-.. versionadded:: 2.3
-    CIDR notation support was introduced in Symfony 2.3, so you can whitelist whole
-    subnets (e.g. ``10.0.0.0/8``, ``fc00::/7``).
-
 .. code-block:: php
 
     use Symfony\Component\HttpFoundation\Request;

components/intl.rst

@@ -8,10 +8,6 @@ The Intl Component
     A PHP replacement layer for the C `intl extension`_ that also provides
     access to the localization data of the `ICU library`_.
 
-.. versionadded:: 2.3
-    The Intl component was introduced in Symfony 2.3. In earlier versions of Symfony,
-    you should use the Locale component instead.
-
 .. caution::
 
     The replacement layer is limited to the locale "en". If you want to use

components/process.rst

@@ -131,9 +131,6 @@ are done doing other stuff::
 Stopping a Process
 ------------------
 
-.. versionadded:: 2.3
-    The ``signal`` parameter of the ``stop`` method was introduced in Symfony 2.3.
-
 Any asynchronous process can be stopped at any time with the
 :method:`Symfony\\Component\\Process\\Process::stop` method. This method takes
 two arguments: a timeout and a signal. Once the timeout is reached, the signal
@@ -170,10 +167,6 @@ To make your code work better on all platforms, you might want to use the
     $builder = new ProcessBuilder(array('ls', '-lsa'));
     $builder->getProcess()->run();
 
-.. versionadded:: 2.3
-    The :method:`ProcessBuilder::setPrefix<Symfony\\Component\\Process\\ProcessBuilder::setPrefix>`
-    method was introduced in Symfony 2.3.
-
 In case you are building a binary driver, you can use the
 :method:`Symfony\\Component\\Process\\ProcessBuilder::setPrefix` method to prefix all
 the generated process commands.
@@ -249,9 +242,6 @@ exceeds 3600 seconds, or the process does not produce any output for 60 seconds.
 Process Signals
 ---------------
 
-.. versionadded:: 2.3
-    The ``signal`` method was introduced in Symfony 2.3.
-
 When running a program asynchronously, you can send it POSIX signals with the
 :method:`Symfony\\Component\\Process\\Process::signal` method::
 
@@ -275,9 +265,6 @@ When running a program asynchronously, you can send it POSIX signals with the
 Process Pid
 -----------
 
-.. versionadded:: 2.3
-    The ``getPid`` method was introduced in Symfony 2.3.
-
 You can access the `pid`_ of a running process with the
 :method:`Symfony\\Component\\Process\\Process::getPid` method.