[Python-Dev] Updated release schedule for 2.6 and 3.0 (original) (raw)
Barry Warsaw barry at python.org
Fri Sep 12 14:54:20 CEST 2008
- Previous message: [Python-Dev] Python 3.0: can we make dbm's .keys() return an iterator?
- Next message: [Python-Dev] [Python-3000] Updated release schedule for 2.6 and 3.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
-----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-----
- Previous message: [Python-Dev] Python 3.0: can we make dbm's .keys() return an iterator?
- Next message: [Python-Dev] [Python-3000] Updated release schedule for 2.6 and 3.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]