minor #6160 remove versionadded for unmaintained versions (xabbuh)

This PR was merged into the 2.7 branch.

Discussion
----------

remove versionadded for unmaintained versions

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | all
| Fixed tickets |

Commits
-------

2eeb2df remove versionadded for unmaintained versions

Author: wouterj

book/forms.rst

@@ -1828,10 +1828,6 @@ section.
     The ``csrf_token_id`` option is optional but greatly enhances the security
     of the generated token by making it different for each form.
 
-.. versionadded:: 2.4
-    The ``csrf_token_id`` option was introduced in Symfony 2.4. Prior, you
-    had to use the ``intention`` option.
-
 .. caution::
 
     CSRF tokens are meant to be different for every user. This is why you

book/testing.rst

@@ -288,9 +288,6 @@ document::
         // ...or simply check that the response is a redirect to any URL
         $this->assertTrue($client->getResponse()->isRedirect());
 
-    .. versionadded:: 2.4
-        Support for HTTP status code constants was introduced in Symfony 2.4.
-
 .. index::
    single: Tests; Client
 

components/event_dispatcher/introduction.rst

@@ -628,10 +628,6 @@ and so on...
 Event Name Introspection
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.4
-    Before Symfony 2.4, the event name and the event dispatcher had to be
-    requested from the ``Event`` instance. These methods are now deprecated.
-
 The ``EventDispatcher`` instance, as well as the name of the event that
 is dispatched, are passed as arguments to the listener::
 

components/form/form_events.rst

@@ -113,9 +113,6 @@ View data        Normalized data transformed using a view transformer
 
 .. sidebar:: ``FormEvents::POST_SET_DATA`` in the Form component
 
-    .. versionadded:: 2.4
-        The data collector extension was introduced in Symfony 2.4.
-
     The ``Symfony\Component\Form\Extension\DataCollector\EventListener\DataCollectorListener``
     class is subscribed to listen to the ``FormEvents::POST_SET_DATA`` event
     in order to collect information about the forms from the denormalized
@@ -226,9 +223,6 @@ View data        Normalized data transformed using a view transformer
 
 .. sidebar:: ``FormEvents::POST_SUBMIT`` in the Form component
 
-    .. versionadded:: 2.4
-        The data collector extension was introduced in Symfony 2.4.
-
     The ``Symfony\Component\Form\Extension\DataCollector\EventListener\DataCollectorListener``
     subscribes to the ``FormEvents::POST_SUBMIT`` event in order to collect
     information about the forms.

components/http_foundation/introduction.rst

@@ -255,9 +255,6 @@ by using the following methods:
 :method:`Symfony\\Component\\HttpFoundation\\Request::getEncodings`
     Returns the list of accepted encodings ordered by descending quality.
 
-    .. versionadded:: 2.4
-        The ``getEncodings()`` method was introduced in Symfony 2.4.
-
 If you need to get full access to parsed data from ``Accept``, ``Accept-Language``,
 ``Accept-Charset`` or ``Accept-Encoding``, you can use
 :class:`Symfony\\Component\\HttpFoundation\\AcceptHeader` utility class::

cookbook/security/csrf_in_login_form.rst

@@ -72,10 +72,6 @@ provider available in the Security component:
             ),
         ));
 
-.. versionadded:: 2.4
-    The ``csrf_token_generator`` option was introduced in Symfony 2.4. Prior,
-    you had to use the ``csrf_provider`` option.
-
 The Security component can be configured further, but this is all information
 it needs to be able to use CSRF in the login form.
 
@@ -184,9 +180,5 @@ After this, you have protected your login form against CSRF attacks.
                 ),
             ));
 
-.. versionadded:: 2.4
-    The ``csrf_token_id`` option was introduced in Symfony 2.4. Prior, you
-    had to use the ``intention`` option.
-
 .. _`Cross-site request forgery`: https://en.wikipedia.org/wiki/Cross-site_request_forgery
 .. _`Forging Login Requests`: https://en.wikipedia.org/wiki/Cross-site_request_forgery#Forging_login_requests

reference/configuration/framework.rst

@@ -526,11 +526,6 @@ profiler
 enabled
 .......
 
-.. versionadded:: 2.2
-    The ``enabled`` option was introduced in Symfony 2.2. Prior to Symfony
-    2.2, the profiler could only be disabled by omitting the ``framework.profiler``
-    configuration entirely.
-
 **type**: ``boolean`` **default**: ``false``
 
 The profiler can be enabled by setting this option to ``true``. When you
@@ -1397,9 +1392,6 @@ error messages.
 strict_email
 ............
 
-.. versionadded:: 2.5
-    The ``strict_email`` option was introduced in Symfony 2.5.
-
 **type**: ``Boolean`` **default**: ``false``
 
 If this option is enabled, the `egulias/email-validator`_ library will be
@@ -1409,9 +1401,6 @@ the validator uses a simple regular expression to validate email addresses.
 api
 ...
 
-.. versionadded:: 2.5
-    The ``api`` option was introduced in Symfony 2.5.
-
 **type**: ``string``
 
 Starting with Symfony 2.5, the Validator component introduced a new validation

reference/configuration/security.rst

@@ -13,15 +13,6 @@ Full Default Configuration
 The following is the full default configuration for the security system.
 Each part will be explained in the next section.
 
-.. versionadded:: 2.5
-    Support for restricting security firewalls to specific http methods was introduced in
-    Symfony 2.5.
-
-.. versionadded:: 2.4
-    The ``csrf_token_generator`` and ``csrf_token_id`` were introduced in
-    Symfony 2.4. Prior, you had to use the ``csrf_provider`` and ``intention``
-    options.
-
 .. configuration-block::
 
     .. code-block:: yaml