-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It's unfortunate that I was not able to release the first betas on Wednesday. The primary reason was that none of the 3.0 buildbots were green.
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.
If we can't get these releases stable by then, Wednesday's release will be alpha and I will make the July 2 release the first beta, updating and pushing back the PEP 361 schedule accordingly.
Thanks for all your help in getting 3.0 stable! - -Barry
2008/6/13 Barry Warsaw barry@python.org:
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?
Regards,
On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista facundobatista@gmail.com wrote:
2008/6/13 Barry Warsaw barry@python.org:
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...
On Fri, Jun 13, 2008 at 9:20 AM, Guido van Rossum guido@python.org wrote:
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.
I will quite happily abide by this; it's already causing more than enough stress over here.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jun 13, 2008, at 9:54 AM, Facundo Batista wrote:
2008/6/13 Barry Warsaw barry@python.org:
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
On Sat, Jun 14, 2008 at 4:18 PM, Barry Warsaw barry@python.org wrote:
On Jun 13, 2008, at 9:54 AM, Facundo Batista wrote:
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.
I kinda hate to do this to you, but I had to file another release blocker: #3114
-
Barry Warsaw -
Benjamin Peterson -
Facundo Batista -
Guido van Rossum