On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista wrote:

2008/6/13 Barry Warsaw :

...

My proposal is this: I will spin another release this coming Wednesday, June 18. If we can get both the 2.6 and 3.0 buildbots green by then, and close out all remaining release critical bugs, then Wednesday's release will be beta 1. In that case, I will update PEP 361 and push the entire schedule back by 2 weeks to account for our slippage.

Next weekend, 21 and 22, it will be the Python Bug days.

Maybe it's worth to delay the betas one week to include this work?

You mean one more week? (Barry's already delaying them one week.) I'm fine with whatever delay Barry approves, but I want EVERYONE to stick to the purpose of the delay: get the buildbots green and close out release critical bugs. This means no new last-minute features or big refactorings (unless there's really no more conservative way to fix a critical bug). It also means try to get at least one other person to review every change, no matter how small (or big!) *before* submitting. It also means run the tests before submitting. On the specific purpose of delaying for the bug day, I'm hesitant -- bug days tend to cause a great deal of commits of code by relatively new developers, which is counter to our purpose of stability. I would almost say it's better for the bug day to fall right after the beta. That also has the advantage that the bug day can focus on new bugs in the beta, and squash them right away... -- --Guido van Rossum (home page: http://www.python.org/~guido/)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jun 13, 2008, at 9:54 AM, Facundo Batista wrote:

2008/6/13 Barry Warsaw :

...

My proposal is this: I will spin another release this coming Wednesday, June 18. If we can get both the 2.6 and 3.0 buildbots green by then, and close out all remaining release critical bugs, then Wednesday's release will be beta 1. In that case, I will update PEP 361 and push the entire schedule back by 2 weeks to account for our slippage.

Next weekend, 21 and 22, it will be the Python Bug days.

Maybe it's worth to delay the betas one week to include this work?

I think I'd rather stick to a one week delay, otherwise I think we're really talking about pushing the whole schedule back a month. I think we should focus right now on getting the buildbots as green as possible (yay for some 3.0 greenness! thanks everyone!) and closing all the release critical bugs. I think this will actually free us up a bit more on bug day to concentrate on fixing other issues. Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSFQ1qnEjvBPtnXfVAQI13wP/Xj+my8YUNHuLG8i7pggHNC1Vn7/j5K7H 4l5vT9EMgkT6OHXKvrVPxOJSbm7TkoHd4k3M524IYwnKigFAVH/e9WmgTChp4hPv 7UsF9MGKcSsgnjB2LpWvbV9A6lSRLsNLjuLqqJSQgS7TvrD+0Omd91RM9twmV9io BndCSNAALyE= =g3RH -----END PGP SIGNATURE-----