[Python-Dev] 2.2.1 release schedule (original) (raw)

Michael Hudson mwh@python.net
18 Mar 2002 14:36:37 +0000

Guido van Rossum <guido@python.org> writes:

> Things are looking as if this might actually happen.

I have one concern: an awful large number of patches went into 2.2.1 in a very short time, and I worry a bit that one release candidate may not be sufficient to make sure that we really didn't introduce any new bugs.

I think the time argument may be a red herring; I'm not sure there are so many people checking the branch out that it really makes any difference.

But I agree there have been a lot of changes, and some pretty subtle ones.

Perhaps we should consider to issue a second release candidate, or at least have a waiting time longer than 1 week between rc and final. (I'd be happy with 2 weeks.)

How about releasing 2.2.1c1, waiting two weeks and then deciding whether we need a c2? In an ideal world, changing the candidate release into a final release would just be a matter of changing version numbers.

Two weeks gets us pretty near Easter; I may not be around so much for the Easter weekend.

Cheers, M.

-- I've reinvented the idea of variables and types as in a programming language, something I do on every project. -- Greg Ward, September 1998