Tagging release candidates, fixing issue 13704
Quick note: Benjamin and I are going to tag our respective branches for release candidates fixing the hash security issue. Haven't heard from Georg yet, but I think we'll wait on the actual rc releases until he's had a chance to tag his branches too.
Thanks everyone for all your really fantastic work on this issue. Experiences like this make me really proud to be part of such a great community.
Cheers, -Barry
Am 23.02.2012 16:48, schrieb Barry Warsaw:
Quick note: Benjamin and I are going to tag our respective branches for release candidates fixing the hash security issue. Haven't heard from Georg yet, but I think we'll wait on the actual rc releases until he's had a chance to tag his branches too.
Since 3.2 is open for general fixes, I'm not working in the main repo. My release repo for 3.2.3 is here: http://hg.python.org/releasing/3.2.3/
Thanks everyone for all your really fantastic work on this issue. Experiences like this make me really proud to be part of such a great community.
+hash("ePjNTUhitHkg")!
Georg
I've now uploaded 2.6.8rc1 to its super sekrit location and added 2.6.8 pages to www.python.org. I won't fiddle the sidebar links until we actually release 2.6.8 final, and I think we're waiting on all the other releases being tagged and ready to do a joint announcement.
You should be able to 2.6.8 by url hacking from the 2.6.7 pages.
Cheers, -Barry
participants (2)
-
Barry Warsaw -
Georg Brandl