Re: [python-committers] branches are open

2011-02-22 Thread Benjamin Peterson
2011/2/21 Georg Brandl : > py3k is now 3.3a0, and I've created a new release32-maint branch. > Thanks to Martin for setting up svnmerge on the new branch; please > merge all bug fixes to release32-maint as usual. > > Benjamin, how long will you want to maintain 3.1 in bugfix mode? I will try to re

Re: [python-committers] branches are open

2011-02-21 Thread Georg Brandl
On 21.02.2011 19:25, Terry Reedy wrote: > > > On 2/21/2011 1:11 PM, Georg Brandl wrote: >> py3k is now 3.3a0, > > Should that be 3.3.0a0, or does adding .0 come later? I'll leave that to the release manager :) Georg ___ python-committers mailing lis

Re: [python-committers] branches are open

2011-02-21 Thread Terry Reedy
On 2/21/2011 1:11 PM, Georg Brandl wrote: py3k is now 3.3a0, Should that be 3.3.0a0, or does adding .0 come later? ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] branches are open

2011-02-21 Thread Georg Brandl
On 21.02.2011 19:11, Georg Brandl wrote: > py3k is now 3.3a0, and I've created a new release32-maint branch. > Thanks to Martin for setting up svnmerge on the new branch; please > merge all bug fixes to release32-maint as usual. One more thing: I've added a 3.2regression keyword to the bug tracker

[python-committers] branches are open

2011-02-21 Thread Georg Brandl
py3k is now 3.3a0, and I've created a new release32-maint branch. Thanks to Martin for setting up svnmerge on the new branch; please merge all bug fixes to release32-maint as usual. Benjamin, how long will you want to maintain 3.1 in bugfix mode? Georg ___