Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-23 Thread Martin v. Löwis
Am 23.10.2010 20:56, schrieb Barry Warsaw: > I will also do any future 2.6 release from svn. It does mean that > patches for those release need to make it into svn. I propose that > only the RM have commit to the svn branches after the switch. This is also my thinking. I would like to see a Mercur

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-23 Thread Barry Warsaw
I will also do any future 2.6 release from svn. It does mean that patches for those release need to make it into svn. I propose that only the RM have commit to the svn branches after the switch. Sent from my digital lollipop. On Oct 23, 2010, at 2:03 PM, "Martin v. Löwis" wrote: > Am 22.10.2

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-23 Thread Benjamin Peterson
2010/10/23 "Martin v. Löwis" : > I'm worried about build identification. Either the switchover happens > before RC1, or after Final. I expect significant breakage from the > Mercurial switchover, so that should all be figured out before or after > the release. I hope that can be well tested before

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-23 Thread Martin v. Löwis
Am 22.10.2010 16:09, schrieb Benjamin Peterson: > 2010/10/22 Dirkjan Ochtman : >> On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson wrote: >>> In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a >>> tentative release schedule: >>> >>> November 13th - RC1 >>> November 27th - RC2 >>

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-22 Thread Benjamin Peterson
2010/10/22 Dirkjan Ochtman : > On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson wrote: >> In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a >> tentative release schedule: >> >> November 13th - RC1 >> November 27th - RC2 >> December 11th - Final > > The last one might clash with

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-22 Thread Georg Brandl
Am 22.10.2010 11:41, schrieb Dirkjan Ochtman: > On Fri, Oct 22, 2010 at 11:06, Georg Brandl wrote: >> If everything goes as planned, there won't be many commits between RC2 and >> final, so it should be fine. The svn repos won't be removed anyway, so >> making a release from them is still possibl

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-22 Thread Dirkjan Ochtman
On Fri, Oct 22, 2010 at 11:06, Georg Brandl wrote: > If everything goes as planned, there won't be many commits between RC2 and > final, so it should be fine.  The svn repos won't be removed anyway, so > making a release from them is still possible. Okay, but accepting commits in both SVN and hg

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-22 Thread Georg Brandl
Am 22.10.2010 09:36, schrieb Dirkjan Ochtman: > On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson wrote: >> In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a >> tentative release schedule: >> >> November 13th - RC1 >> November 27th - RC2 >> December 11th - Final > > The last on

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-22 Thread Dirkjan Ochtman
On Fri, Oct 22, 2010 at 00:57, Benjamin Peterson wrote: > In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a > tentative release schedule: > > November 13th - RC1 > November 27th - RC2 > December 11th - Final The last one might clash with the hg migration a bit, do we need to w

Re: [Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-21 Thread Barry Warsaw
On Oct 21, 2010, at 05:57 PM, Benjamin Peterson wrote: >In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a >tentative release schedule: > >November 13th - RC1 >November 27th - RC2 >December 11th - Final Sounds like you're planning to get finals out this year, not next :). +1 f

[Python-Dev] 3.1.3 and 2.7.1 release schedule

2010-10-21 Thread Benjamin Peterson
In the interest of getting 3.1.3 and 2.7.1 out by next year, here's a tentative release schedule: November 13th - RC1 November 27th - RC2 December 11th - Final I'll jump for it if there are no objections. -- Regards, Benjamin ___ Python-Dev mailing li