I'm not a core developer, but here's the current situation as far as I can tell.
There's been a steady stream of about releases blocker coming in almost once per day, most of them migrations related: https://code.djangoproject.com/query?version=!master&resolution=fixed&severity=Release+blocker&or&status=assigned&status=new&version=!master&severity=Release+blocker&col=id&col=summary&col=version&col=status&col=time&col=changetime&desc=1&order=id So my guess is: once it feels like there aren't any more release blockers coming in (maybe a few days without a release blocker), the next step will likely be to put out another release candidate. In order to put out the final 1.7 release, this release candidate would need to be out and have few major bugs for at least two weeks, otherwise we'd need to do yet another release candidate. So, like Florian said, the more we can test the latest 1.7.x code especially migrations, the sooner we can discover and fix the major bugs. -- 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/9fdbbd92-cc07-4f22-9a89-e394566d03d8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
