[Python-Dev] [Python-3000] Proposed revised schedule (original) (raw)

Guido van Rossum guido at python.org
Tue Sep 9 01:25:10 CEST 2008

On Mon, Sep 8, 2008 at 4:13 PM, Benjamin Peterson <musiccomposition at gmail.com> wrote:

On Mon, Sep 8, 2008 at 12: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. I'm not really sure what good that would do us unless we wanted to bring 3.0 back to the beta phase and continue to work on some larger issues with it. I also suspect doing two separate, but close together final releases would be more stressful than having them in lock and step.

Well, from the number of release blockers it sounds like another 3.0 beta is the right thing. For 2.6 however I believe we're much closer to the finish line -- there aren't all those bytes/str issues to clean up, for example! And apparently the benefit of releasing on schedule is that we will be included in OSX. That's a much bigger deal for 2.6 than for 3.0 (I doubt that Apple would add two versions anyway).

Just my pocket change, though.

-- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."

-- --Guido van Rossum (home page: http://www.python.org/~guido/)

More information about the Python-Dev mailing list