-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 13, 2008, at 9:54 AM, Facundo Batista wrote:
2008/6/13 Barry Warsaw [EMAIL PROTECTED]:
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
On Sat, Jun 14, 2008 at 4:18 PM, Barry Warsaw [EMAIL PROTECTED] 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,
2008/6/13 Barry Warsaw [EMAIL PROTECTED]:
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
On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista
[EMAIL PROTECTED] wrote:
2008/6/13 Barry Warsaw [EMAIL PROTECTED]:
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
On Fri, Jun 13, 2008 at 7:27 AM, Georg Brandl [EMAIL PROTECTED] wrote:
Guido van Rossum schrieb:
On Fri, Jun 13, 2008 at 6:54 AM, Facundo Batista
[EMAIL PROTECTED] wrote:
2008/6/13 Barry Warsaw [EMAIL PROTECTED]:
My proposal is this: I will spin another release this coming Wednesday,
June
On Fri, Jun 13, 2008 at 9:20 AM, Guido van Rossum [EMAIL PROTECTED] 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
