Re: [python-committers] 2.7.2 and 3.1.4 rc now

2011-05-29 Thread Eli Bendersky
>> Just to be sure, you mean the 3.1.4 will be the last bugfix release? 3.1.5 >> will >> be security fix only? So for example, as Python 2.6, doc updates are no more >> accepted in 3.1? > > Correct. > That's great. Shorter pull dances for all :) Eli __

Re: [python-committers] 2.7.2 and 3.1.4 rc now

2011-05-29 Thread Benjamin Peterson
2011/5/29 Victor Stinner : > 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. > > Just to be sure, you mean

Re: [python-committers] 2.7.2 and 3.1.4 rc now

2011-05-29 Thread Victor Stinner
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. Just to be sure, you mean the 3.1.4 will be the last bugfix r

[python-committers] 2.7.2 and 3.1.4 rc now

2011-05-29 Thread Benjamin Peterson
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. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org h

Re: [python-committers] Merge cleanup reminder

2011-05-29 Thread Éric Araujo
Hi, Le 29/05/2011 12:00, Ned Deily a écrit : > Just a reminder and an FYI: the repo was left yesterday with an unmerged > change leaving the 3.2 branch open. When you're finished pushing > changes, it's always a good head idea to do an "hg branches" and make > sure that only the default (py3k)

Re: [python-committers] Merge cleanup reminder

2011-05-29 Thread Ned Deily
In article , "Gregory P. Smith" wrote: > Thanks. It looks like I did my merge incorrectly, I'll revisit my hg > procedures. > > *flogs self* Thanks! P.S. I have no idea what "a good head idea" is supposed to be. > On Sun, May 29, 2011 at 3:00 AM, Ned Deily wrote: >>When you're finished pushi

Re: [python-committers] Merge cleanup reminder

2011-05-29 Thread Gregory P. Smith
On Sun, May 29, 2011 at 3:00 AM, Ned Deily wrote: > Just a reminder and an FYI: the repo was left yesterday with an unmerged > change leaving the 3.2 branch open. When you're finished pushing > changes, it's always a good head idea to do an "hg branches" and make > sure that only the default (py

[python-committers] Merge cleanup reminder

2011-05-29 Thread Ned Deily
Just a reminder and an FYI: the repo was left yesterday with an unmerged change leaving the 3.2 branch open. When you're finished pushing changes, it's always a good head idea to do an "hg branches" and make sure that only the default (py3k) and 2.7 branches are open: $ hg branches default