[python-committers] Why r69846 is not merged to "release26-maint"?
David Goodger
goodger at python.org
Sat Jul 4 00:32:52 CEST 2009
More information about the python-committers mailing list
Sat Jul 4 00:32:52 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 Fri, Jul 3, 2009 at 18:27, Jesus Cea<jcea at jcea.es> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Brett Cannon wrote: >> 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. > > If that is true (I agree with that policy, btw), please confirm > "officially". Barry announced it as officially as possible: http://mail.python.org/pipermail/python-list/2009-July/718561.html I followed up with a python.org front-page news item & PSF blog entry (both linking to that message on python-list). > Can we forget about 3.0 branch?. Can I delete that > checkout from my system?. Seems so. -- David Goodger <http://python.net/~goodger>
- 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