I have been waiting for something like this for a very long time. No more wondering where signals should go. [0]
[0]https://docs.djangoproject.com/en/dev/ref/applications/#djan...
For anyone coming to Django from Rails, South seems anomalous. Outside of database migrations, Django is a very battery-included framework, so it's weird that until 1.7 data migrations were handled by third party tools (mostly South) and not mentioned at all in the Django documentation.
This is a big step for Django. I'm excited for the (not too distant) future when 1.7 is the official release.
* Apply all South migrations to all database servers,
* Delete South migrations,
* Create new initial (create table) migrations for the current schema.
This makes sense, as migration code is supposed to be temporary. Migrations should exist in the codebase until the last database has them applied. Once all databases are up-to-date, it's better to delete them and "rebase" migrations to the current schema.
Old, fully applied migrations will still stay documented in the version control history, but they shouldn't be part of the master tree, much like obsolete code should be deleted instead of left commented out.
Anybody have any insight into what's next?
Is this because of the new migrations built-in module? [0]
The ./manage.py validate command has been replaced with ./manage.py check in Django 1.7. The new system checks framework [1] is extensible, so third party apps will be able to add their own checks.
