symfony · weaverryan · May 4, 2013 · Apr 24, 2013
diff --git a/book/forms.rst b/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;

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

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

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

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

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

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

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

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

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

diff --git a/components/filesystem.rst b/components/filesystem.rst
@@ -6,10 +6,6 @@ The Filesystem Component
 
     The Filesystem components provides basic utilities for the filesystem.
 
-.. versionadded:: 2.1
-    The Filesystem Component is new to Symfony 2.1. Previously, the ``Filesystem``
-    class was located in the ``HttpKernel`` component.
-
 Installation
 ------------
 

diff --git a/components/finder.rst b/components/finder.rst
@@ -182,9 +182,6 @@ The ``notName()`` method excludes files matching a pattern::
 File Contents
 ~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-   The ``contains()`` and ``notContains()`` methods were added in version 2.1
-
 Restrict files by contents with the
 :method:`Symfony\\Component\\Finder\\Finder::contains` method::
 
@@ -243,9 +240,6 @@ Restrict by a size range by chaining calls::
 The comparison operator can be any of the following: ``>``, ``>=``, ``<``, ``<=``,
 ``==``, ``!=``.
 
-.. versionadded:: 2.1
-   The operator ``!=`` was added in version 2.1.
-
 The target value may use magnitudes of kilobytes (``k``, ``ki``), megabytes
 (``m``, ``mi``), or gigabytes (``g``, ``gi``). Those suffixed with an ``i`` use
 the appropriate ``2**n`` version in accordance with the `IEC standard`_.
@@ -296,9 +290,6 @@ instance. The file is excluded from the result set if the Closure returns
 Reading contents of returned files
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-   Method ``getContents()`` have been introduced in version 2.1.
-
 The contents of returned files can be read with
 :method:`Symfony\\Component\\Finder\\SplFileInfo::getContents`::
 

diff --git a/components/http_foundation/introduction.rst b/components/http_foundation/introduction.rst
@@ -387,9 +387,6 @@ To redirect the client to another URL, you can use the
 Streaming a Response
 ~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    Support for streamed responses was added in Symfony 2.1.
-
 The :class:`Symfony\\Component\\HttpFoundation\\StreamedResponse` class allows
 you to stream the Response back to the client. The response content is
 represented by a PHP callable instead of a string::
@@ -421,9 +418,6 @@ represented by a PHP callable instead of a string::
 Serving Files
 ~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The ``makeDisposition`` method was added in Symfony 2.1.
-
 When sending a file, you must add a ``Content-Disposition`` header to your
 response. While creating this header for basic file downloads is easy, using
 non-ASCII filenames is more involving. The
@@ -480,10 +474,6 @@ right content and headers. A JSON response might look like this::
     )));
     $response->headers->set('Content-Type', 'application/json');
 
-.. versionadded:: 2.1
-    The :class:`Symfony\\Component\\HttpFoundation\\JsonResponse`
-    class was added in Symfony 2.1.
-
 There is also a helpful :class:`Symfony\\Component\\HttpFoundation\\JsonResponse`
 class, which can make this even easier::
 

diff --git a/components/http_foundation/sessions.rst b/components/http_foundation/sessions.rst
@@ -9,10 +9,6 @@ The Symfony2 HttpFoundation Component has a very powerful and flexible session
 subsystem which is designed to provide session management through a simple
 object-oriented interface using a variety of session storage drivers.
 
-.. versionadded:: 2.1
-    The :class:`Symfony\\Component\\HttpFoundation\\Session\\SessionInterface` interface,
-    as well as a number of other changes, are new as of Symfony 2.1.
-
 Sessions are used via the simple :class:`Symfony\\Component\\HttpFoundation\\Session\\Session`
 implementation of :class:`Symfony\\Component\\HttpFoundation\\Session\\SessionInterface` interface.
 

diff --git a/components/http_kernel/introduction.rst b/components/http_kernel/introduction.rst
@@ -447,9 +447,6 @@ method, which sends the headers and prints the ``Response`` content.
 8) The ``kernel.terminate`` event
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The ``kernel.terminate`` event is new to Symfony 2.1.
-
 **Typical Purposes**: To perform some "heavy" action after the response has
 been streamed to the user
 

diff --git a/components/process.rst b/components/process.rst
@@ -61,9 +61,6 @@ anonymous function to the
         }
     });
 
-.. versionadded:: 2.1
-    The non-blocking feature was added in 2.1.
-
 You can also start the subprocess and then let it run asynchronously, retrieving
 output and the status in your main process whenever you need it. Use the 
 :method:`Symfony\\Component\\Process\\Process::start` method to start an asynchronous
@@ -107,9 +104,6 @@ instead::
     );
     $process->run();
 
-.. versionadded:: 2.1
-    The ``ProcessBuilder`` class was added in Symfony 2.1.
-
 To make your code work better on all platforms, you might want to use the
 :class:`Symfony\\Component\\Process\\ProcessBuilder` class instead::
 

diff --git a/cookbook/bundles/extension.rst b/cookbook/bundles/extension.rst
@@ -510,9 +510,6 @@ For more details, see :doc:`/cookbook/bundles/prepend_extension`.
 Default Configuration Dump
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The ``config:dump-reference`` command was added in Symfony 2.1
-
 The ``config:dump-reference`` command allows a bundle's default configuration to
 be output to the console in yaml.
 

diff --git a/cookbook/configuration/pdo_session_storage.rst b/cookbook/configuration/pdo_session_storage.rst
@@ -14,13 +14,6 @@ Symfony2 has a built-in solution for database session storage called
 To use it, you just need to change some parameters in ``config.yml`` (or the
 configuration format of your choice):
 
-.. versionadded:: 2.1
-    In Symfony2.1 the class and namespace are slightly modified. You can now 
-    find the session storage classes in the `Session\\Storage` namespace:
-    ``Symfony\Component\HttpFoundation\Session\Storage``. Also
-    note that in Symfony2.1 you should configure ``handler_id`` not ``storage_id`` like in Symfony2.0. 
-    Below, you'll notice that ``%session.storage.options%`` is not used anymore.
-
 .. configuration-block::
 
     .. code-block:: yaml

diff --git a/cookbook/console/sending_emails.rst b/cookbook/console/sending_emails.rst
@@ -20,9 +20,6 @@ and per Command.
 Configuring the Request Context globally
 ----------------------------------------
 
-.. versionadded:: 2.1
-    The ``host`` and ``scheme`` parameters are available since Symfony 2.1
-
 .. versionadded: 2.2
     The ``base_url`` parameter is available since Symfony 2.2
 

diff --git a/cookbook/doctrine/resolve_target_entity.rst b/cookbook/doctrine/resolve_target_entity.rst
@@ -5,10 +5,6 @@
 How to Define Relationships with Abstract Classes and Interfaces
 ================================================================
 
-.. versionadded:: 2.1
-    The ResolveTargetEntityListener is new to Doctrine 2.2, which was first
-    packaged with Symfony 2.1.
-
 One of the goals of bundles is to create discreet bundles of functionality
 that do not have many (if any) dependencies, allowing you to use that
 functionality in other applications without including unnecessary items.

diff --git a/cookbook/form/data_transformers.rst b/cookbook/form/data_transformers.rst
@@ -177,11 +177,6 @@ its error message can be controlled with the ``invalid_message`` field option.
 Model and View Transformers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 2.1
-    The names and method of the transformers were changed in Symfony 2.1.
-    ``prependNormTransformer`` became ``addModelTransformer`` and ``appendClientTransformer``
-    became ``addViewTransformer``.
-
 In the above example, the transformer was used as a "model" transformer.
 In fact, there are two different type of transformers and three different
 types of underlying data.

diff --git a/cookbook/form/form_collections.rst b/cookbook/form/form_collections.rst
@@ -390,9 +390,6 @@ HTML contains the tag ``text`` input element with a name of ``task[tags][__name_
 and id of ``task_tags___name___name``. The ``__name__`` is a little "placeholder",
 which you'll replace with a unique, incrementing number (e.g. ``task[tags][3][name]``).
 
-.. versionadded:: 2.1
-    The placeholder was changed from ``$$name$$`` to ``__name__`` in Symfony 2.1
-
 The actual code needed to make this all work can vary quite a bit, but here's
 one example:
 

diff --git a/cookbook/logging/channels_handlers.rst b/cookbook/logging/channels_handlers.rst
@@ -4,10 +4,6 @@
 How to log Messages to different Files
 ======================================
 
-.. versionadded:: 2.1
-    The ability to specify channels for a specific handler was added to
-    the MonologBundle for Symfony 2.1.
-
 The Symfony Standard Edition contains a bunch of channels for logging: ``doctrine``,
 ``event``, ``security`` and ``request``. Each channel corresponds to a logger
 service (``monolog.logger.XXX``) in the container and is injected to the