[Python-Dev] Re: python/dist/src/Lib/bsddb init.py,1.5,1.6 (original) (raw)

Brett C. bac at OCF.Berkeley.EDU
Mon Sep 15 14:20:21 EDT 2003

Jeremy Hylton wrote:

On Mon, 2003-09-15 at 08:51, A.M. Kuchling wrote:

I'd be in favor of setting an arbitrary date for a 2.4 release, and when that date rolls around stabilizing and releasing the CVS tree, no matter what's been implemented or not implemented. If we've made major language revisions by that time, fine, but it's worthwhile even if 2.4 is just 2.3 + (various bugfixes deemed too risky for 2.3.1) + (a few new modules).

PEP 320 estimates February 2005, a 19-month gap matching that between 2.2 and 2.3. That seems a bit too long, especially if there are no large changes that require testing; aiming for autumn 2004, beginning to freeze in August, seems reasonable. In the absence of any plans for major new features, I think this is a good plan. A rough schedule might be: 2.4a1 April 2.4a2 late May/early June 2.4b1 July 9 2.4b2 Aug. 6 2.4 f Sep. 3

+1

We could also try to schedule micro releases two months after the initial release. That seems to have been a decent amount of time to get in bug reports and fix them. Then again, standardizing micro releases might cause people to hold off on using the newest release and thus we might get less testing from users.

-Brett

More information about the Python-Dev mailing list