[python-committers] Why r69846 is not merged to "release26-maint"?
"Martin v. Löwis"
martin at v.loewis.de
Thu Jul 2 21:01:35 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 21:01:35 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 ]
> The particulars of the revision control system don't matter as much > as the discipline of teaching people to commit fixes. Right now, we > have 2.6.x, 3.0.x and 3.1.x. > > > 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. Regards, Martin
- 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