diff options
author | Stephen Finucane <stephen.finucane@intel.com> | 2015-11-02 20:18:04 +0000 |
---|---|---|
committer | Stephen Finucane <stephen.finucane@intel.com> | 2015-11-05 15:48:12 +0000 |
commit | 819642e0ff7a4165ed6f57d1d35edb1e814745d1 (patch) | |
tree | ff08516dd6778c261f11f239eb8915aa3440fa41 /UPGRADING.md | |
parent | 9af5386937a3ce62c5931424fbda5e2366140490 (diff) | |
download | patchwork-819642e0ff7a4165ed6f57d1d35edb1e814745d1.tar patchwork-819642e0ff7a4165ed6f57d1d35edb1e814745d1.tar.gz |
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>
Diffstat (limited to 'UPGRADING.md')
-rw-r--r-- | UPGRADING.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/UPGRADING.md b/UPGRADING.md index 3cf69d4..b302716 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 |