symfony · wouterj · Jan 5, 2015
diff --git a/book/controller.rst b/book/controller.rst
@@ -520,9 +520,6 @@ console command:
 
     $ php app/console debug:container
 
-.. versionadded:: 2.6
-    Prior to Symfony 2.6, this command was called ``container:debug``.
-
 For more information, see the :doc:`/book/service_container` chapter.
 
 .. index::

diff --git a/book/forms.rst b/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

diff --git a/book/routing.rst b/book/routing.rst
@@ -1386,9 +1386,6 @@ the command by running the following from the root of your project.
 
     $ php app/console debug:router
 
-.. versionadded:: 2.6
-    Prior to Symfony 2.6, this command was called ``router:debug``.
-
 This command will print a helpful list of *all* the configured routes in
 your application:
 

diff --git a/book/security.rst b/book/security.rst
@@ -805,10 +805,6 @@ You can easily deny access from inside a controller::
         // ...
     }
 
-.. versionadded:: 2.6
-     The ``security.authorization_checker`` service was introduced in Symfony 2.6. Prior
-     to Symfony 2.6, you had to use the ``isGranted()`` method of the ``security.context`` service.
-
 .. versionadded:: 2.5
     The ``createAccessDeniedException`` method was introduced in Symfony 2.5.
 
@@ -979,10 +975,6 @@ shown above.
 Retrieving the User Object
 --------------------------
 
-.. versionadded:: 2.6
-     The ``security.token_storage`` service was introduced in Symfony 2.6. Prior
-     to Symfony 2.6, you had to use the ``getToken()`` method of the ``security.context`` service.
-
 After authentication, the ``User`` object of the current user can be accessed
 via the ``security.token_storage`` service. From inside a controller, this will
 look like::
@@ -1179,9 +1171,6 @@ in the following way from a controller::
 
     $user->setPassword($encoded);
 
-.. versionadded:: 2.6
-    The ``security.password_encoder`` service was introduced in Symfony 2.6.
-
 In order for this to work, just make sure that you have the encoder for your
 user class (e.g. ``AppBundle\Entity\User``) configured under the ``encoders``
 key in ``app/config/security.yml``.

diff --git a/book/service_container.rst b/book/service_container.rst
@@ -1132,9 +1132,6 @@ console. To show all services and the class for each service, run:
 
     $ php app/console debug:container
 
-.. versionadded:: 2.6
-    Prior to Symfony 2.6, this command was called ``container:debug``.
-
 By default, only public services are shown, but you can also view private services:
 
 .. code-block:: bash

diff --git a/book/templating.rst b/book/templating.rst
@@ -1178,12 +1178,6 @@ automatically:
             <p>Application Environment: <?php echo $app->getEnvironment() ?></p>
         <?php endif ?>
 
-.. versionadded:: 2.6
-    The global ``app.security`` variable (or the ``$app->getSecurity()``
-    method in PHP templates) is deprecated as of Symfony 2.6. Use `app.user` 
-    (`$app->getUser()`) and `is_granted()` (`$view['security']->isGranted()`)
-    instead.
-
 .. tip::
 
     You can add your own global template variables. See the cookbook example

diff --git a/book/testing.rst b/book/testing.rst
@@ -414,11 +414,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::
 
@@ -461,9 +456,6 @@ Be warned that this does not work if you insulate the client or if you use an
 HTTP layer. For a list of services available in your application, use the
 ``debug:container`` console task.
 
-.. versionadded:: 2.6
-    Prior to Symfony 2.6, this command was called ``container:debug``.
-
 .. tip::
 
     If the information you need to check is available from the profiler, use

diff --git a/book/translation.rst b/book/translation.rst
@@ -400,9 +400,6 @@ checks translation resources for several locales:
 #. If the translation still isn't found, Symfony uses the ``fallback`` configuration
    parameter, which defaults to ``en`` (see `Configuration`_).
 
-.. versionadded:: 2.6
-    The ability to log missing translations was introduced in Symfony 2.6.
-
 .. note::
 
     When Symfony doesn't find a translation in the given locale, it will 
@@ -673,9 +670,6 @@ Debugging Translations
 .. versionadded:: 2.5
     The ``debug:translation`` command was introduced in Symfony 2.5.
 
-.. versionadded:: 2.6
-    Prior to Symfony 2.6, this command was called ``translation:debug``.
-
 When maintaining a bundle, you may use or remove the usage of a translation
 message without updating all message catalogues. The ``debug:translation``
 command helps you to find these missing or unused translation messages for a

diff --git a/components/config/definition.rst b/components/config/definition.rst
@@ -290,10 +290,6 @@ method.
 
 The info will be printed as a comment when dumping the configuration tree.
 
-.. versionadded:: 2.6
-    Since Symfony 2.6, the info will also be added to the exception message
-    when an invalid type is given.
-
 Optional Sections
 -----------------
 

diff --git a/components/console/events.rst b/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::
@@ -54,9 +51,6 @@ dispatched. Listeners receive a
 Disable Commands inside Listeners
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.6
-    Disabling commands inside listeners was introduced in Symfony 2.6.
-
 Using the
 :method:`Symfony\\Component\\Console\\Event\\ConsoleCommandEvent::disableCommand`
 method, you can disable a command inside a listener. The application

diff --git a/components/console/helpers/debug_formatter.rst b/components/console/helpers/debug_formatter.rst
@@ -4,9 +4,6 @@
 Debug Formatter Helper
 ======================
 
-.. versionadded:: 2.6
-    The Debug Formatter helper was introduced in Symfony 2.6.
-
 The :class:`Symfony\\Component\\Console\\Helper\\DebugFormatterHelper` provides
 functions to output debug information when running an external program, for
 instance a process or HTTP request. It is included in the default helper set

diff --git a/components/console/helpers/dialoghelper.rst b/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
 ................
 

diff --git a/components/console/helpers/processhelper.rst b/components/console/helpers/processhelper.rst
@@ -4,9 +4,6 @@
 Process Helper
 ==============
 
-.. versionadded:: 2.6
-    The Process Helper was introduced in Symfony 2.6.
-
 The Process Helper shows processes as they're running and reports
 useful information about process status.
 

diff --git a/components/console/helpers/progressbar.rst b/components/console/helpers/progressbar.rst
@@ -44,22 +44,11 @@ Instead of advancing the bar by a number of steps (with the
 you can also set the current progress by calling the
 :method:`Symfony\\Component\\Console\\Helper\\ProgressBar::setProgress` method.
 
-.. versionadded:: 2.6
-    The ``setProgress()`` method was called ``setCurrent()`` prior to Symfony 2.6.
-
 .. caution::
 
     Prior to version 2.6, the progress bar only works if your platform
     supports ANSI codes; on other platforms, no output is generated.
 
-.. versionadded:: 2.6
-    If your platform doesn't support ANSI codes, updates to the progress
-    bar are added as new lines. To prevent the output from being flooded,
-    adjust the
-    :method:`Symfony\\Component\\Console\\Helper\\ProgressBar::setRedrawFrequency`
-    accordingly. By default, when using a ``max``, the redraw frequency
-    is set to *10%* of your ``max``.
-
 If you don't know the number of steps in advance, just omit the steps argument
 when creating the :class:`Symfony\\Component\\Console\\Helper\\ProgressBar`
 instance::
@@ -307,9 +296,6 @@ that displays the number of remaining steps::
         }
     );
 
-.. versionadded:: 2.6
-    The ``getProgress()`` method was called ``getStep()`` prior to Symfony 2.6.
-
 Custom Messages
 ~~~~~~~~~~~~~~~
 

diff --git a/components/console/helpers/progresshelper.rst b/components/console/helpers/progresshelper.rst
@@ -4,9 +4,6 @@
 Progress Helper
 ===============
 
-.. versionadded:: 2.3
-    The ``setCurrent`` method was introduced in Symfony 2.3.
-
 .. versionadded:: 2.4
     The ``clear`` method was introduced in Symfony 2.4.
 

diff --git a/components/console/helpers/tablehelper.rst b/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

diff --git a/components/console/introduction.rst b/components/console/introduction.rst
@@ -170,10 +170,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`:
 

diff --git a/components/debug/introduction.rst b/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
 ------------
 

diff --git a/components/dependency_injection/factories.rst b/components/dependency_injection/factories.rst
@@ -4,11 +4,6 @@
 Using a Factory to Create Services
 ==================================
 
-.. versionadded:: 2.6
-    The new :method:`Symfony\\Component\\DependencyInjection\\Definition::setFactory`
-    method was introduced in Symfony 2.6. Refer to older versions for the
-    syntax for factories prior to 2.6.
-
 Symfony's Service Container provides a powerful way of controlling the
 creation of objects, allowing you to specify arguments passed to the constructor
 as well as calling methods and setting parameters. Sometimes, however, this

diff --git a/components/dependency_injection/lazy_services.rst b/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?
 ------------------
 

diff --git a/components/dom_crawler.rst b/components/dom_crawler.rst
@@ -193,10 +193,6 @@ Get all the child or parent nodes::
 Accessing Node Values
 ~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.6
-    The :method:`Symfony\\Component\\DomCrawler\\Crawler::nodeName`
-    method was introduced in Symfony 2.6.
-
 Access the node name (HTML tag name) of the first node of the current selection (eg. "p" or "div")::
 
     // will return the node name (HTML tag name) of the first child element under <body>
@@ -230,11 +226,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.
 

diff --git a/components/expression_language/extending.rst b/components/expression_language/extending.rst
@@ -56,9 +56,6 @@ evaluating or the "names" if compiling).
 Using Expression Providers
 --------------------------
 
-.. versionadded:: 2.6
-    Expression providers were introduced in Symfony 2.6.
-
 When you use the ``ExpressionLanguage`` class in your library, you often want
 to add custom functions. To do so, you can create a new expression provider by
 creating a class that implements

diff --git a/components/filesystem/introduction.rst b/components/filesystem/introduction.rst
@@ -241,9 +241,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.

diff --git a/components/filesystem/lock_handler.rst b/components/filesystem/lock_handler.rst
@@ -1,9 +1,6 @@
 LockHandler
 ===========
 
-.. versionadded:: 2.6
-    The lock handler feature was introduced in Symfony 2.6
-
 What is a Lock?
 ---------------
 

diff --git a/components/finder.rst b/components/finder.rst
@@ -93,10 +93,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__);