Skip to content

Commit

Permalink
[1.7.x] Refs #25144 -- Revised deprecation timeline: migrations won't…
Browse files Browse the repository at this point in the history
… become compulsory.

Backport of e133b55 from master
  • Loading branch information
timgraham committed Sep 4, 2015
1 parent c0f9957 commit 2d2eeff
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions docs/internals/deprecation.txt
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,12 @@ details on these changes.
* ``allow_syncdb`` on database routers will no longer automatically become
``allow_migrate``.

* The legacy method of syncing apps without migrations will be removed,
and migrations will become compulsory for all apps. This includes automatic
loading of ``initial_data`` fixtures and support for initial SQL data.
* Automatic syncing of apps without migrations will be removed. Migrations will
become compulsory for all apps unless you pass the ``--run-syncdb`` option to
``migrate``.

* Support for automatic loading of ``initial_data`` fixtures and initial SQL
data will be removed.

* All models will need to be defined inside an installed application or
declare an explicit :attr:`~django.db.models.Options.app_label`.
Expand Down

0 comments on commit 2d2eeff

Please sign in to comment.