From e133b55943f26e87cff5b22215a776a9ce3fc6f3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 31 Aug 2015 10:40:45 -0400 Subject: [PATCH] Refs #25144 -- Revised deprecation timeline: migrations won't become compulsory. --- docs/internals/deprecation.txt | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt index c2d92fd866..96ad90dd92 100644 --- a/docs/internals/deprecation.txt +++ b/docs/internals/deprecation.txt @@ -289,9 +289,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`.