Would love some concrete guidance on this if anyone can work out exactly what needs to happen. It sounds like all that's left to do for 1.7 support is to move all our south migrations into different directories and create new 1.7 style initial migrations, but I've not had the time to work this out properly.
If anyone could work this out definitively and create a pull request, you'd really be helping out. On Thu, Sep 4, 2014 at 6:42 AM, Tom Lockhart <[email protected]> wrote: > > On 2014-09-03, at 8:24 AM, Eduardo Rivas <[email protected]> wrote: > > > Just noticed Django supports having both types of migrations coexist. > Apparently all that needs to be done is renaming migrations to > south_migrations. > https://docs.djangoproject.com/en/1.7/topics/migrations/#libraries-third-party-apps > > Yup. Just heard a talk on this from Andrew Godwin at DjangoCon here in > Portland. Native migrations will re-use the migrations/ directory and if > you want to maintain a South history then move previous migrations over to > south_migrations/. Though once you are at 1.7 I'm not sure why you would > need to go back; Andrew indicated that most of the code for migrations is > new but they have been testing and bugfixing for several months already. > > hth > > - Tom > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Stephen McDonald http://jupo.org -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
