On Tue, Jul 1, 2008 at 4:23 PM, Georg Brandl <g.brandl@gmx.net> wrote:

Barry Warsaw schrieb:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Wow, I bet this one crept up on you as quickly as it did me!

We have our second planned beta releases for 2.6 and 3.0 tomorrow. As usual I will start looking at blockers and buildbots tomorrow afternoon (UTC-4 time) with a plan to start building things at about 6pm. Also, I will of course be in #python-dev on freenode to answer any questions, or get second opinions.

PEP 361 claims that these will be the last betas. Whether that's true or not depends on how well the beta2's go. Please help review code or fix bugs. If you know of things that absolutely must go into beta2, be sure there is an open release-blocker bug on the issue.

May I ask if it really makes sense to release the beta tomorrow? Looking at the Misc/NEWS files for 2.6 and 3.0, there are around 3-5 entries for each release. I know it's good to follow the release plan, but it also may save you, the release manager, work for the third beta (which I think will be necessary if beta2 is released tomorrow).

Georg

Speaking from my minor perspective - I've been sick and MIA, so there has not been a lot of movement on the pep 371 issues / multiprocessing bugs since Beta 1, there's still a fair amount of issues to close out. -jesse