On Sep 8, 2008, at 1:13 PM, "Guido van Rossum" <guido at python.org> wrote: > On Mon, Sep 8, 2008 at 6:23 AM, Barry Warsaw <barry at python.org> wrote: >> I don't think there's any way we're going to make our October 1st >> goal. We >> have 8 open release critical bugs, and 18 deferred blockers. We do >> not have >> a beta3 Windows installer and I don't have high hopes for >> rectifying all of >> these problems in the next day or two. >> >> I propose that we push the entire schedule back two weeks. This >> means that >> the planned rc2 on 17-September becomes our rc1. The planned final >> release >> for 01-October becomes our rc2, and we release the finals on 15- >> October. >> >> - -Barry > > Perhaps it's time to separate the 2.6 and 3.0 release schedules? I > don't care if the next version of OSX contains 3.0 or not -- but I do > care about it having 2.6. > Given that 2.6 is going to be more widely adopted and used by both the community and OS distributors, I'm +1 on splitting the releases as well. -Jesse
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4