Changelog entry for 5.11.0
- Legacy-Id: 9030
This commit is contained in:
parent
63f8de29d7
commit
ea8fa17472
23
changelog
23
changelog
|
@ -4,17 +4,22 @@ ietfdb (5.11.0) ietf; urgency=medium
|
|||
0.12.1. It changes the database migrations infrastructure from that provided
|
||||
by "south", to the builtin replacement newly introduced with Django 1.7.
|
||||
|
||||
There are also a set of changes required by the upgrade, and some fixes
|
||||
to bugs revealed by the improved infrastructure provided by Django 1.7.
|
||||
There are also a number of changes which are required by the upgrade, in
|
||||
order to make things work as expected, and some fixes to bugs revealed by
|
||||
the improved infrastructure provided by Django 1.7.
|
||||
|
||||
Deployment note: When deploying this, migrations need some extra care.
|
||||
You should run the following:
|
||||
$ ietf/manage.py migrate --fake doc
|
||||
$ ietf/manage.py migrate --fake community
|
||||
$ ietf/manage.py migrate --fake dbtemplate
|
||||
$ ietf/manage.py migrate
|
||||
Deployment note:
|
||||
|
||||
-- Henrik Levkowetz <henrik@levkowetz.com> 08 Feb 2015 21:02:38 +0000
|
||||
When deploying this, migrations need some extra care, as the new-style
|
||||
migrations which are part of the release should not actually be run -- they
|
||||
are there to provide a status snapshot as a basis for future migrations.
|
||||
|
||||
In order to handle this, please use the --fake option when running migrations
|
||||
for this particular release:
|
||||
|
||||
$ ietf/manage.py migrate --fake
|
||||
|
||||
-- Henrik Levkowetz <henrik@levkowetz.com> 09 Feb 2015 20:17:05 +0000
|
||||
|
||||
|
||||
ietfdb (5.10.3) ietf; urgency=medium
|
||||
|
|
Loading…
Reference in a new issue