Le samedi 29 janvier 2011 à 12:24 +0000, Vinay Sajip a écrit : > > > > So my "pronouncement" here is: if reviewed properly, the patch will go > > in 3.2rc2. If this needs a few more days, so be it. And should the > > testing after 3.2rc2 reveal deficiencies, we will fix them and put in > > another rc. > > > > +1. > > When we say "release candidate", surely that implies no known serious > brokenness. Even if we have to go back to calling it beta (Marc-Andre's > point), > surely there's no harm in that, as long as it's made clear that it wouldn't > be a > free-for-all for other patches to go in?
Okay, I don't mind if mailbox gets "fixed", but -1 on making the release schedule any longer because of that. OTOH, if mailbox *needs* a lengthening of the release schedule, then it's 3.3 material (or 3.2.1, depending on the other RM's view :-)). Regards Antoine. _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
