Add documentation for removed Django 1.6 support

docs/source/internals/contributing/development-environment.rst

@@ -84,4 +84,4 @@ up an environment with both installed and do the following:
     ./test_migrations.sh
 
     This will recreate the Oscar database in both MySQL and Postgres and rebuild
-    it using ``syncdb`` and ``migrate``.
+    it using ``migrate``.

docs/source/internals/getting_started.rst

@@ -238,37 +238,15 @@ Check your database settings. A quick way to get started is to use SQLite:
 Note that we recommend using ``ATOMIC_REQUESTS`` to tie transactions to
 requests.
 
-Migrations
-----------
-
-Oscar ships with two sets of migrations. If you're running Django 1.7, you
-don't need to do anything; Django's migration framework will detect them
-automatically and will do the right thing.
-If you're running Django 1.6, you need to install `South`_:
-
-.. code-block:: bash
-
-    $ pip install South
-
-And you need to add it to your installed apps:
-
-.. code-block:: django
-
-    INSTALLED_APPS = [
-        ...
-        'south',
-    ] + get_core_apps()
-
-.. _South: http://south.readthedocs.org/en/latest/
-
-Create Database
+Create database
 ---------------
 
-Then create the database and the shop should be browsable:
+Oscar ships with migrations. Django's migration framework will detect them
+automatically and will do the right thing.
+Create the database and the shop should be browsable:
 
 .. code-block:: bash
 
-    $ python manage.py syncdb --noinput  # Only needed for Django 1.6
     $ python manage.py migrate
     $ python manage.py runserver
 

docs/source/releases/v1.1.rst

@@ -21,6 +21,10 @@ Table of contents:
 Compatibility
 -------------
 
+Oscar 1.1 is compatible with Django 1.7 and Django 1.8, and Python 2.7,
+3.3 and 3.4.  Support for Django 1.6, and hence South for migrations, has been
+removed.
+
 
 .. _new_in_1.1:
 
@@ -129,6 +133,10 @@ If you have customised any app, please consult the
    This release contains a data migration for category slugs.  If you have
    forked it, it is critical you run a copy of that migration when upgrading.
 
+.. warning::
+   This release doesn't include any South migrations, as support for Django
+   1.6 has been dropped.
+
 Catalogue
   * This app contains model changes.
   * This app contains a data migration: ``0003_data_migration_slugs``.
@@ -151,6 +159,27 @@ Removal of deprecated features
 
 These methods have been removed:
 
+* ``oscar.core.compat.atomic_compat``: Use ``django.db.transaction.atomic``
+  instead.
+* ``oscar.core.loading.import_string``: Use
+  ``django.utils.module_loading.import_string`` instead.
+* ``Product.variants``: Use ``Product.children``
+* ``Product.is_top_level``: Use ``Product.is_standalone or self.is_parent``
+* ``Product.is_group``: Use ``Product.is_parent``
+* ``Product.is_variant``: Use ``Product.is_child``
+* ``Product.min_variant_price_incl_tax``: Refactor or use the deprecated
+  ``Product.min_child_price_incl_tax``.
+* ``Product.min_variant_price_excl_tax``: Refactor or use the deprecated
+  ``Product.min_child_price_excl_tax``.
+* ``Strategy.fetch_for_group``: Use ``Strategy.fetch_for_parent``.
+* ``Strategy.select_variant_stockrecords``: Use
+  ``Strategy.select_children_stockrecords``.
+* ``Strategy.group_pricing_policy``: Use ``Strategy.parent_pricing_policy``.
+* ``Strategy.group_availability_policy``: Use
+  ``Strategy.parent_availability_policy``.
 
 These classes have been removed:
 
+These instances have been removed:
+
+* ``oscar.app.shop``: Use ``oscar.app.application`` instead.