[python-committers] 2.7.2 and 3.1.4 rc now

Tue May 31 07:19:54 CEST 2011

Am 30.05.2011 23:36, schrieb Benjamin Peterson:
> 2011年5月30日 Victor Stinner <victor.stinner at haypocalc.com>:
>> Le dimanche 29 mai 2011 22:55:17, Benjamin Peterson a écrit :
>>> Hi,
>>> I'm going to start spinning those releases now. I'll make a branch for
>>> 2.7.2 but not for 3.1.4. Please stop committing to 3.1; it's going
>>> into security only mode.
>>>> I would like to commit something into the 2.7 branch. The NEWS file starts
>> with:
>>>> What's New in Python 2.7.2?
>> ===========================
>>>> *Release date: 2011年05月29日*
>>>> Python 2.7.2 was released yesterday, or was it the RC1?
>>>> I don't care if my commit (better fix for #1195) doesn't go into Python 2.7.2,
>> so should I start an empty "Python 2.7.3" section?
>> Yes, go ahead.

Really??? I have some changes that I need to commit to 2.7 that do need
to go into 2.7.2. So how are you going to manage these?
I rather recommend that the 2.7 branch is frozen until the final
release, and any changes are only merged afterwards.
This is a mess.
Regards,
Martin