docs: Emphasise the deprecation of Django 1.6

Though already mentioned in the CHANGELOG, the UPGRADING document
should describe plans to deprecate support for Django 1.6. This will
ensure sysadmins are not suprised when they attempt to upgrade.

Signed-off-by: Stephen Finucane <stephen.finucane@intel.com>

diff --git a/UPGRADING.md b/UPGRADING.md
index 3cf69d4864d871492c2aff0b10246a7b33442167..b302716694b3803f59a643debae76492e2a9eb65 100644 (file)
--- a/UPGRADING.md
+++ b/UPGRADING.md
@@ -13,6 +13,10 @@ and re-run the grants script. For example, on postgres:
     psql -f lib/sql/migration/015-add-patch-tags.sql patchwork
     psql -f lib/sql/grant-all.postgres.sql patchwork
 
+We highly suggest you move to Django Migrations as support for Django 1.6
+(and subsequently manual SQL migrations) will be dropped in an upcoming
+release.
+
 ### Update to the new settings infrastructure
 
 By default, settings are read from `patchwork/settings/production.py`. To