Bug 1116335 - Updated migration docs.

docs/installation-vagrant.rst

@@ -223,12 +223,12 @@ If you see the same error over and over, please ask for :ref:`more help <more-he
 
 .. _puppet: http://puppetlabs.com/puppet/puppet-open-source
 
-kuma_south_migrate
-~~~~~~~~~~~~~~~~~~
+kuma_migrate
+~~~~~~~~~~~~
 
 If you see errors like::
 
-    notice: /Stage[main]/Kuma_config/Exec[kuma_south_migrate]
+    notice: /Stage[main]/Kuma_config/Exec[kuma_migrate]
 
 try to manually run database migrations in the vm. To do so::
 

docs/migrations.rst

@@ -1,29 +1,14 @@
 Migrations
 ==========
 
-South-managed apps and DB tables
---------------------------------
+Basically all apps are migrated using Django's migration system.
 
-Basically all apps are migrated using South. We used to use a different
-migration tool side by side with South. But that's ancient history.
-
-You can `convert an app over to South <http://south.aeracode.org/docs/convertinganapp.html#converting-an-app>`_, if it doesn't have
-migrations yet, for great justice.
+See the Django documentation for the
+`migration workflow <https://docs.djangoproject.com/en/1.8/topics/migrations/#workflow>`_.
 
 How to run the migrations
 -------------------------
 
-Run South via its Django management command::
-
-    python2.6 manage.py migrate
-
-Where are the migrations?
--------------------------
-
-South migrations for first-party, non-vendor apps are in a ``migrations``
-subdirectory. For example, check out ``kuma/demos/migrations``.
+Run the migrations via the Django management command::
 
-South migrations for third-party apps under ``vendor/`` are found in python
-modules under ``migrations/south/`` and are activated by adding them to
-``SOUTH_MIGRATION_MODULES`` in ``settings.py``. See
-`the South docs <http://south.aeracode.org/docs/settings.html#setting-south-migration-modules>`_ about this.
+    python manage.py migrate