Removed all versionadded older than 0.7

docs/contrib/frontendcache.rst

@@ -3,8 +3,6 @@
 Frontend cache invalidation
 ===========================
 
-.. versionadded:: 0.4
-
 .. versionchanged:: 0.7
 
    * Multiple backend support added

docs/contrib/routablepage.rst

@@ -4,8 +4,6 @@
 Embedding URL configuration in Pages
 ====================================
 
-.. versionadded:: 0.6
-
 The ``RoutablePageMixin`` mixin provides a convenient way for a page to respond on multiple sub-URLs with different views. For example, a blog section on a site might provide several different types of index page at URLs like ``/blog/2013/06/``, ``/blog/authors/bob/``, ``/blog/tagged/python/``, all served by the same ``BlogIndex`` page.
 
 A ``Page`` using ``RoutablePageMixin`` exists within the page tree like any other page, but URL paths underneath it are checked against a list of patterns, using Django's urlconf scheme. If none of the patterns match, control is passed to subpages as usual (or failing that, a 404 error is thrown).

docs/contrib/sitemaps.rst

@@ -3,8 +3,6 @@
 Sitemap generation
 ==================
 
-.. versionadded:: 0.4
-
 This document describes how to create XML sitemaps for your Wagtail website using the ``wagtail.contrib.wagtailsitemaps`` module.
 
 

docs/howto/performance.rst

@@ -48,6 +48,4 @@ Caching proxy
 
 To support high volumes of traffic with excellent response times, we recommend a caching proxy. Both `Varnish <http://www.varnish-cache.org/>`_ and `Squid <http://www.squid-cache.org/>`_ have been tested in production. Hosted proxies like `Cloudflare <https://www.cloudflare.com/>`_ should also work well.
 
-.. versionadded:: 0.4
-
-    Wagtail supports automatic cache invalidation for Varnish/Squid. See :ref:`frontend_cache_purging` for more information.
+ Wagtail supports automatic cache invalidation for Varnish/Squid. See :ref:`frontend_cache_purging` for more information.

docs/images/using_in_templates.rst

@@ -131,8 +131,6 @@ Wagtail provides two shortcuts to give greater control over the ``img`` element:
 
 **1. Adding attributes to the  {% image %} tag**
 
-.. versionadded:: 0.4
-
 Extra attributes can be specified with the syntax ``attribute="value"``:
 
 .. code-block:: django
@@ -170,8 +168,6 @@ Therefore in the above example, if you'd added the field ``foo`` to your Abstrac
 The ``attrs`` shortcut
 -----------------------
 
-.. versionadded:: 0.4
-
 You can also use the ``attrs`` property as a shorthand to output the attributes ``src``, ``width``, ``height`` and ``alt`` in one go:
 
 .. code-block:: django

docs/pages/advanced_topics/private_pages.rst

@@ -3,8 +3,6 @@
 Private pages
 =============
 
-.. versionadded:: 0.4
-
 Users with publish permission on a page can set it to be private by clicking the 'Privacy' control in the top right corner of the page explorer or editing interface, and setting a password. Users visiting this page, or any of its subpages, will be prompted to enter a password before they can view the page.
 
 Private pages work on Wagtail out of the box - the site implementer does not need to do anything to set them up. However, the default "password required" form is only a bare-bones HTML page, and site implementers may wish to replace this with a page customised to their site design.

docs/reference/hooks.rst

@@ -6,9 +6,6 @@ Hooks
 
 On loading, Wagtail will search for any app with the file ``wagtail_hooks.py`` and execute the contents. This provides a way to register your own functions to execute at certain points in Wagtail's execution, such as when a ``Page`` object is saved or when the main menu is constructed.
 
-.. versionadded:: 0.5
-  Decorator syntax was added in 0.5; earlier versions only supported ``hooks.register`` as an ordinary function call.
-
 Registering functions with a Wagtail hook is done through the ``@hooks.register`` decorator:
 
 .. code-block:: python
@@ -32,7 +29,6 @@ The available hooks are:
 .. _before_serve_page:
 
 ``before_serve_page``
-  .. versionadded:: 0.4
 
   Called when Wagtail is about to serve a page. The callable passed into the hook will receive the page object, the request object, and the args and kwargs that will be passed to the page's ``serve()`` method. If the callable returns an ``HttpResponse``, that response will be returned immediately to the user, and Wagtail will not proceed to call ``serve()`` on the page.
 
@@ -48,8 +44,6 @@ The available hooks are:
 
 .. _construct_wagtail_userbar:
 
-.. versionadded:: 0.3
-
 .. versionchanged:: 1.0
 
    The hook was renamed from ``construct_wagtail_edit_bird``
@@ -159,7 +153,6 @@ The available hooks are:
 .. _register_admin_menu_item:
 
 ``register_admin_menu_item``
-  .. versionadded:: 0.6
 
   Add an item to the Wagtail admin menu. The callable passed to this hook must return an instance of ``wagtail.wagtailadmin.menu.MenuItem``. New items can be constructed from the ``MenuItem`` class by passing in a ``label`` which will be the text in the menu item, and the URL of the admin page you want the menu item to link to (usually by calling ``reverse()`` on the admin view you've set up). Additionally, the following keyword arguments are accepted:
 
@@ -253,7 +246,6 @@ The available hooks are:
 .. _construct_whitelister_element_rules:
 
 ``construct_whitelister_element_rules``
-.. versionadded:: 0.4
 
   Customise the rules that define which HTML elements are allowed in rich text areas. By default only a limited set of HTML elements and attributes are whitelisted - all others are stripped out. The callables passed into this hook must return a dict, which maps element names to handler functions that will perform some kind of manipulation of the element. These handler functions receive the element as a `BeautifulSoup <http://www.crummy.com/software/BeautifulSoup/bs4/doc/>`_ Tag object.