Updated release schedule for 2.6 and 3.0
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We had a lot of discussion recently about changing the release schedule and splitting Python 2.6 and 3.0. There was general consensus that this was a good idea, in order to hit our October 1 deadline for Python 2.6 final at least. There is only one open blocker for 2.6, issue 3657. Andrew, Fred, Tim and I (via IRC) will be getting together tonight to do some Python hacking, so we should resolve this issue and release 2.6rc1 tonight. We'll have an abbreviated 2.6rc1, and I will release 2.6rc2 next Wednesday the 17th as planned. The final planned release of 2.6 will be Wednesday October 1st. If 3.0 is looking better, I will release 3.0rc1 on Wednesday, otherwise we'll re-evaluate the release schedule for 3.0 as necessary. This means currently the schedule looks like this: Fri 12-Sep 2.6rc1 Wed 17-Sep 2.6rc2, 3.0rc1 Wed 01-Oct 2.6 final, 3.0rc2 Wed 15-Oct 3.0 final I've updated the Python Release Schedule gcal and will update the PEP momentarily. We'll close the tree later tonight (UTC-4). - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMpmfHEjvBPtnXfVAQJUiQP/eTXStyp9M0+Ja7iAFfYcpzfM19j9ddBr ocMC+KTDSgci5/rmFw4KdMhqO9TBk2sXIdCd9GInnuMOKtndCKZ/PXaexnVvSVGb P3CpkkMs/vG1itQIc/EXq6CUhzwuxEv9h8Wo8+zcmL05Cc1IrE5d2OYiO0+KQ8ei lW+j/aNKMWY= =w2oI -----END PGP SIGNATURE-----
On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw <barry@python.org> wrote:
We had a lot of discussion recently about changing the release schedule and splitting Python 2.6 and 3.0. There was general consensus that this was a good idea, in order to hit our October 1 deadline for Python 2.6 final at least.
Does it matter to anyone besides the you, the Python developers, whether the schedule slips by two weeks, or two months, for that matter? I am underwhelmed by 3.0 b3: sax and 2to3 are/were broken. A b4 release for 3.0 (at least) would seem more prudent. Edward
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sep 12, 2008, at 9:19 AM, Edward K. Ream wrote:
On Fri, Sep 12, 2008 at 7:54 AM, Barry Warsaw <barry@python.org> wrote:
We had a lot of discussion recently about changing the release schedule and splitting Python 2.6 and 3.0. There was general consensus that this was a good idea, in order to hit our October 1 deadline for Python 2.6 final at least.
Does it matter to anyone besides the you, the Python developers, whether the schedule slips by two weeks, or two months, for that matter?
For Python 3.0? No.
I am underwhelmed by 3.0 b3: sax and 2to3 are/were broken. A b4 release for 3.0 (at least) would seem more prudent.
We will release no Python before its time. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSMpsr3EjvBPtnXfVAQKCUQP/WYfGeubbkWjmwI9mlQ4dMbVjGk15imAJ ArIBs4sH9tbZTE12uNhjNgvXRbN+1QfejNeWOEJEAnPdErPAT0TKAmgA2Rj1MmjP ook5+MbxkgkNnKbz8lozMPduclc7Djf22CYboAqiskK7G6LfD1fsCrIMEVSku/HX dQpXGkG/C4g= =FYgJ -----END PGP SIGNATURE-----
participants (2)
-
Barry Warsaw -
Edward K. Ream