Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

2012-09-30 Thread Georg Brandl
On 10/01/2012 04:29 AM, Jesus Cea wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/09/12 10:35, Georg Brandl wrote: Until the last ordinary 3.2 bugfix release is done (which will be soon), the usual procedure for 3.x will be to check into 3.2, merge into 3.3, and then merge into defau

Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

2012-09-30 Thread Benjamin Peterson
2012/9/30 Jesus Cea : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 29/09/12 10:35, Georg Brandl wrote: >> Until the last ordinary 3.2 bugfix release is done (which will be >> soon), the usual procedure for 3.x will be to check into 3.2, merge >> into 3.3, and then merge into default, ex

Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

2012-09-30 Thread Terry Reedy
On 9/30/2012 10:29 PM, Jesus Cea wrote: So, if I understand correctly, the current situation is this: 2.6: Security fixes only 2.7, 3.2, 3.3: Bugfixes only 2.3, 2.4, 2.5, 3.0, 3.1: Dead After 3.2.4 is published ("soon"), 3.2 would move to "security fixes only". Am I right? I wonder if we ha

[python-committers] Branches support status (Re: 3.3 branch created in main repository)

2012-09-30 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/09/12 10:35, Georg Brandl wrote: > Until the last ordinary 3.2 bugfix release is done (which will be > soon), the usual procedure for 3.x will be to check into 3.2, merge > into 3.3, and then merge into default, except of course for a) > fixes of