[python-committers] Why r69846 is not merged to "release26-maint"?
Anthony Baxter
anthonybaxter at gmail.com
Thu Jul 2 20:29:25 CEST 2009
More information about the python-committers mailing list
Thu Jul 2 20:29:25 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 ]
I think Barry should totally cut a completely pointless 3.0.2 release. We can call it the "homage to 1.6" release. <god-I've-been-involved-with-python-too-long/> Anthony On Fri, Jul 3, 2009 at 4:24 AM, Barry Warsaw <barry at python.org> wrote: > On Jul 2, 2009, at 1:56 PM, 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. >> > > Right. There have been rumblings of wanting a 3.0.2, and I could do it if > the clamor were loud enough, but I still think we don't need one. > > -Barry > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20090703/7e26be9d/attachment-0001.htm>
- 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