p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[1.8.x] Fixed #23892 -- Clarified compatibility policy for migrations. 

Backport of e35c70bef4 from master
This commit is contained in:
Carl Meyer 2015-02-15 12:40:13 -07:00 committed by Tim Graham
parent bc2eb6bfef
commit e63d9b98e7
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/topics/migrations.txt
View File

@ -750,6 +750,20 @@ next run of :djadmin:`makemigrations` on Python 3 will likely generate many
changes as it converts all the bytestring attributes to text strings; this is changes as it converts all the bytestring attributes to text strings; this is
normal and should only happen once. normal and should only happen once.
Supporting multiple Django versions
-----------------------------------
If you are the maintainer of a third-party app with models, you may need to
ship migrations that support multiple Django versions. In this case, you should
always run :djadmin:`makemigrations` **with the lowest Django version you wish
to support**.
The migrations system will maintain backwards-compatibility according to the
same policy as the rest of Django, so migration files generated on Django X.Y
should run unchanged on Django X.Y+1. The migrations system does not promise
forwards-compatibility, however. New features may be added, and migration files
generated with newer versions of Django may not work on older versions.
.. _upgrading-from-south: .. _upgrading-from-south:
Upgrading from South Upgrading from South