The "Upgrading from South" documentation
https://docs.djangoproject.com/en/dev/topics/migrations/#upgrading-from-
south should mention that as a solution for re-usable applications as a
way to provide backward compatible release but also with new migrations.
--
Ticket URL: <https://code.djangoproject.com/ticket/23127>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* severity: Normal => Release blocker
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I guess it wouldn't hurt to point this out here in order to help third
party applications move to the migration framework while supporting South
in the same code base.
--
Ticket URL: <https://code.djangoproject.com/ticket/23127#comment:1>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"b9a9b052e8b4a47504abc0f14be3087aaa700e47"]:
{{{
#!CommitTicketReference repository=""
revision="b9a9b052e8b4a47504abc0f14be3087aaa700e47"
Fixed #23127: south_migrations note in docs
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23127#comment:2>
Comment (by Andrew Godwin <andrew@…>):
In [changeset:"cc875e94cf6c18530595a59e91ecd23f5c961146"]:
{{{
#!CommitTicketReference repository=""
revision="cc875e94cf6c18530595a59e91ecd23f5c961146"
[1.7.x] Fixed #23127: south_migrations note in docs
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23127#comment:3>