The Python 2.6.6 announcement is going out in a few minutes. First, thanks to
*everyone* who helped make this a great release.
Second, this is just a reminder that Python 2.6 is now in security-fix-only
mode. There will not be another maintenance release, so please, while the
tree is thawed, only security critical patches to release26-maint are
allowed. If in doubt, contact me on irc and use the bug tracker (make it a
release blocker issue as usual). You can also discuss the issue on
security(a)python.org if you need a more private forum.
From now on Python 2.6 will be released source-only.
 svnmerge blocks are of course still allowed, as are Martin's Windows
I will be tagging the 2.6.6 final release in a little while. I'm sure I don't
need to say it, but please no commits to release26-maint until further
notice. I am on #python-dev for any last minute questions or problems.
Python 2.6.6rc2 is tagged and uploaded (source tarballs). The website's been
twiddled. Martin will update with Windows information tomorrow. I'll then
send out the wider announcement.
You are going to have to make a very generous FLUFLy offering to commit
anything new into release26-maint now. :)
Hi Martin, this is the tag to use to build 2.6.6rc2.
Begin forwarded message:
Date: Tue, 17 Aug 2010 00:58:42 +0200 (CEST)
From: barry.warsaw <python-checkins(a)python.org>
Subject: [Python-checkins] r84119 - python/tags/r266rc2
Date: Tue Aug 17 00:58:41 2010
New Revision: 84119
- copied from r84118, /python/branches/release26-maint/
Python-checkins mailing list
Does anyone have an issue with me requesting commit privs for Ask
Solem to help me with the multiprocessing module? He's the author of
the celery package (http://celeryproject.org/) and one of the biggest
multiprocessing users I know of. He's also submitted several patches,
and I consult with him on bigger changes.
As it stands, I've not had the time I need or want to dedicate to
focusing on fixes, therefore I feel it would be beneficial to pull in
a second person to help distribute the load. I would of course mentor
him, and coordinate with him for the foreseeable future.
I'm liking where we're at for Python 2.6.6. We have no release blocker issues
open, and the buildbots look about as green as they get. I've accounted for
all the commits since 2.6.6rc1 and I think barring any last minute issues,
that we're on schedule for 2.6.6 final for this Monday, August 16.
Please, no commits to release26-maint without checking with me first (svnmerge
blocks are okay). I plan to tag the release at approximately 2200 UTC Monday
so that Martin can build the Windows binaries first thing on Tuesday and I can
announce the release Tuesday afternoon EST.
I'll be hanging out on #python-dev as much as possible over the weekend in
case anything crops up.
Thanks to everybody who has helped get 2.6.6 to such an awesome state.
-----BEGIN PGP SIGNED MESSAGE-----
How is migration to Mercurial going?. Showstoppers?.
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea(a)jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
jabber / xmpp:email@example.com _/_/ _/_/ _/_/_/_/_/
. _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----