From: Stephen Finucane Date: Mon, 2 Nov 2015 20:18:04 +0000 (+0000) Subject: docs: Emphasise the deprecation of Django 1.6 X-Git-Tag: v1.1.0~138 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=819642e0ff7a4165ed6f57d1d35edb1e814745d1;p=thirdparty%2Fpatchwork.git 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 --- diff --git a/UPGRADING.md b/UPGRADING.md index 3cf69d48..b3027166 100644 --- 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