[python-committers] rc2 freeze due in two days
Georg Brandl
georg at python.org
Sat Jan 29 15:27:59 CET 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 29.01.2011 13:52, schrieb Antoine Pitrou:
> 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 :-)).
Not if it's a few days, otherwise I'd agree.
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1EI+8ACgkQN9GcIYhpnLCpqACglNZB0ZKLbif+7ruxqIRJn/63
nQkAn1wW5dm3EDNKqbrGXxbBE2w998rO
=Rqgw
-----END PGP SIGNATURE-----
More information about the python-committers
mailing list