2 weeks later and we still have a fairly strong stream of new bugs (thanks everyone for testing), so I wouldn't expect a second RC until next week at the earliest.
There was a suggestion among the core team to release another RC (even if the list of release blockers isn't zero). This would make testing easier and help us avoid getting duplicate bug reports for issues fixed since RC1, but others were against it: "We should not release RC2 until there are 0 release blockers, though - remember, an RC is supposed to be identical to the final release if there's no blockers." Opinions from the community on that would be welcome. On Thursday, July 10, 2014 5:49:10 PM UTC-4, Tim Graham wrote: > > It's been 2 weeks since the release of 1.7 RC1 and we've seen several bugs > opened and fixed, with several still open [1]. We plan to issue a second RC > sometime next week if we can empty that list. Help us fix the issues if you > have some time and keep testing! > > [1] > https://code.djangoproject.com/query?status=assigned&status=new&version=!master&severity=Release+blocker&col=id&col=summary&col=status&col=owner&col=type&col=component&col=changetime&desc=1&order=changetime > -- 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/89fb0487-7828-42e2-a85b-b63be9c28db8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
