On Fri, Aug 9, 2013 at 9:36 PM, Andrew Godwin <[email protected]> wrote:
> Hi everyone, > > I think it's finally time to look at merging the schema-alteration branch, > which has gone slightly beyond its name and encompasses the schema > alteration backends and the migration code as well. > > The branch is working, well tested, moderately documented and has all of > the big changes that happen to other parts of Django outside of the > migration code (removing syncdb, changing signals, changes to the Field API > - see the 1.7 release notes in the branch for more). > > It's not quite release quality yet - quite a bit of polish remains - but > it's functional, and I want to merge it now as merging changes back in from > master is becoming trickier and trickier. > > You can see the pull request here: > > https://github.com/django/django/pull/376 > > I'd be aiming to merge this early next week, dependent on feedback. > Say… Andrew… there's this guy on a black horse at my front door… says his name is "Famine"… he wants to talk about the coming apocalypse… :-) Seriously -- great news, and fantastic work. I'll do what I can to give this a review some time this week; I'd encourage everyone else to do the same if they can. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
