[python-committers] Why r69846 is not merged to "release26-maint"?
Mark Dickinson
dickinsm at gmail.com
Thu Jul 2 22:49:06 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 22:49:06 CEST 2009
- Previous message: [python-committers] Why r69846 is not merged to"release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Jul 2, 2009 at 8:01 PM, "Martin v. Löwis"<martin at v.loewis.de> wrote: > [Brett] >> If I remember correctly I believe we decided at the language summit that >> 3.0 is just dead now that 3.1 is out and we shouldn't even bother with >> another point release since 3.1 followed 3.0 so closely and didn't >> introduce any new syntax or tweak semantics. > > Unfortunately, that decision was never communicated to the committers, > or, for that matter, to people present at the language summit :-( > > So people have continued to merge to 3.0. I think they deserve a 3.0.2 > release. Speaking as one of the people who occasionally remembers to backport to 3.0 (though clearly I failed with r69846), it wouldn't bother me at all if there were no 3.0.2. I can't speak for any of the other backporters, of course. I'm not really sure who 3.0.2 would be useful for. Mark
- Previous message: [python-committers] Why r69846 is not merged to"release26-maint"?
- Next message: [python-committers] Why r69846 is not merged to "release26-maint"?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list