On Mon, Apr 21, 2014 at 11:35 PM, Andrew Godwin <[email protected]> wrote:
> Yes, no matter what it's too late to add anything to 1.7, which is a > massive shame - we'll have to just heavily document this for now, and then > investigate the dump/load data stuff for the next cycle (I think it should > work everywhere initial_data did, at least, as they're both fixtures). > Are we absolutely sure about this? Process is meant to be a tool to ensure quality, not the other way around. Put it this way - if we push out 1.7 with migrations with their current feature set, are we going to be mobbed by people saying that migrations are broken? As much as a deferred release would pain me, I'd rather see a few weeks delay than release documentation that has to explain a bunch of edge cases that get cleaned up in the next release. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq8499%3D7ytzMEBbjmtPd7zgc4JJKn1HiC8Fvjf6QErgP_qGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
