Add versionadded tags to many ffeatures in the docs.

docs/en/reference/dql-doctrine-query-language.rst

@@ -410,6 +410,8 @@ Get all users that have no phonenumber
 Get all instances of a specific type, for use with inheritance
 hierarchies:
 
+.. versionadded:: 2.1
+
 .. code-block:: php
 
     <?php
@@ -419,6 +421,8 @@ hierarchies:
 
 Get all users visible on a given website that have chosen certain gender:
 
+.. versionadded:: 2.3
+
 .. code-block:: php
 
     <?php

docs/en/reference/filters.rst

@@ -1,6 +1,8 @@
 Filters
 =======
 
+.. versionadded:: 2.2
+
 Doctrine 2.2 features a filter system that allows the developer to add SQL to
 the conditional clauses of queries, regardless the place where the SQL is
 generated (e.g. from a DQL query, or by loading associated entities).

docs/en/reference/namingstrategy.rst

@@ -1,6 +1,8 @@
 Implementing a NamingStrategy
 ==============================
 
+.. versionadded:: 2.3
+
 Using a naming strategy you can provide rules for automatically generating
 database identifiers, columns and tables names
 when the table/column name is not given.
@@ -145,4 +147,4 @@ Just set your naming strategy calling ``Doctrine\ORM\Configuration#setNamingStra
 
     <?php
     $namingStrategy = new MyAppNamingStrategy();
-    $configuration()->setNamingStrategy($namingStrategy);
+    $configuration()->setNamingStrategy($namingStrategy);

docs/en/reference/working-with-objects.rst

@@ -731,6 +731,8 @@ examples are equivalent:
 By Criteria
 ~~~~~~~~~~~
 
+.. versionadded:: 2.3
+
 The Repository implement the ``Doctrine\Common\Collections\Selectable``
 interface. That means you can build ``Doctrine\Common\Collections\Criteria``
 and pass them to the ``matching($criteria)`` method.

docs/en/tutorials/composite-primary-keys.rst

@@ -1,6 +1,8 @@
 Composite and Foreign Keys as Primary Key
 =========================================
 
+.. versionadded:: 2.1
+
 Doctrine 2 supports composite primary keys natively. Composite keys are a very powerful relational database concept
 and we took good care to make sure Doctrine 2 supports as many of the composite primary key use-cases.
 For Doctrine 2.0 composite keys of primitive data-types are supported, for Doctrine 2.1 even foreign keys as

docs/en/tutorials/extra-lazy-associations.rst

@@ -1,6 +1,8 @@
 Extra Lazy Associations
 =======================
 
+.. versionadded:: 2.1
+
 In many cases associations between entities can get pretty large. Even in a simple scenario like a blog.
 where posts can be commented, you always have to assume that a post draws hundreds of comments.
 In Doctrine 2.0 if you accessed an association it would always get loaded completely into memory. This

docs/en/tutorials/pagination.rst

@@ -1,6 +1,8 @@
 Pagination
 ==========
 
+.. versionadded:: 2.2
+
 Starting with version 2.2 Doctrine ships with a Paginator for DQL queries. It
 has a very simple API and implements the SPL interfaces ``Countable`` and
 ``IteratorAggregate``.