Home Original page

[python-committers] 2.7.2 and 3.1.4 rc now

Benjamin Peterson benjamin at python.org
Tue May 31 15:18:14 CEST 2011 
2011/5/31 "Martin v. Löwis" <martin at v.loewis.de>:
> 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 have a release branch from the 2.7.2rc1. It's currently, local, but
I will push it (when I get to a computer with my .ssh keys), so you
can apply any changes you need to it. Then after 2.7.2, I will merge
it to the 2.7 branch.

>
> I rather recommend that the 2.7 branch is frozen until the final
> release, and any changes are only merged afterwards.




-- 
Regards,
Benjamin
More information about the python-committers mailing list