2.2.1 release mechanics
I'm aware that I've not been great about keeping people up to date about my timing plans for the last couple of releases, so I'd like to be a little more organized this time. My plan goes roughly as follows: April 8 ~1200 GMT: freeze begins. Over the next 24 hours I'll do tests, write Misc/NEWS, update version numbers, etc. April 9 ~1200 GMT: freeze ends, release begins. This is when Fred, Tim and Jack do their magic, and check any changes they have to make into the tree. I'd really like to get the Mac release done at the same time as the others. During this time, I'll draft changes to python.org and an announcement. April 10 ~1200 GMT: release ends By now, F, T & J have done their bits, uploaded files to creosote and sf (or pointed me to where I can get them), etc. I twiddle pages on creosote, fiddle with sf, tag the tree, cut the tarball, compute md5s, etc. The cunning will notice that this doesn't require me to be in the office after half past five... Does this plan sound reasonable to everyone? Cheers, M. -- I don't have any special knowledge of all this. In fact, I made all the above up, in the hope that it corresponds to reality. -- Mark Carroll, ucam.chat
Michael Hudson writes:
April 10 ~1200 GMT: release ends
By now, F, T & J have done their bits, uploaded files to creosote and sf (or pointed me to where I can get them), etc.
Are we still on target for this? -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
[Michael Hudson]
April 10 ~1200 GMT: release ends
By now, F, T & J have done their bits, uploaded files to creosote and sf (or pointed me to where I can get them), etc.
[Fred]
Are we still on target for this?
I expect so, but it's gotten confused. Since I got up today <wink>, + I'm building a 2.1.3 Windows installer too. + I believe we're no longer uploading anything to SF, although I'm not sure Michael and Anthony both believe that. + A very recent msg from Guido said we were releasing 2.2.1 today too, which is ahead of Michael's schedule (in response to the 2.1.3 Windows semi-surprise, I had intended to push 2.2.1 Windows off to Tuesday night).
I expect so, but it's gotten confused. Since I got up today <wink>,
+ I'm building a 2.1.3 Windows installer too.
Which you offered to do earlier this weekend.
+ I believe we're no longer uploading anything to SF, although I'm not sure Michael and Anthony both believe that.
AFAIK they were cc'ed on the msgs where that was decided.
+ A very recent msg from Guido said we were releasing 2.2.1 today too, which is ahead of Michael's schedule (in response to the 2.1.3 Windows semi-surprise, I had intended to push 2.2.1 Windows off to Tuesday night).
Fine with me. I didn't mean the reference to "tonight" as a directive to the release manager, it was what *I* believed, sorry if I was wrong. This is Michael's call. --Guido van Rossum (home page: http://www.python.org/~guido/)
[Tim]
I expect so, but it's gotten confused. Since I got up today <wink>,
+ I'm building a 2.1.3 Windows installer too.
[Guido]
Which you offered to do earlier this weekend.
Sure, but it was left undecided then -- I offer to do a lot of things it turns out nobody wants <wink>.
+ I believe we're no longer uploading anything to SF, although I'm not sure Michael and Anthony both believe that.
AFAIK they were cc'ed on the msgs where that was decided.
Then perhaps I wasn't. I only deduced it indirectly from one piece of email that *suggested* it might be the case, buried in a layer or two of quoting. So I believe it's prudent to make sure everyone who was supposed to get that email actually did (esp. since I don't believe I did, unless it's hiding in one of the 100+ new "stability" emails I haven't had time to open yet).
+ A very recent msg from Guido said we were releasing 2.2.1 today too, which is ahead of Michael's schedule (in response to the 2.1.3 Windows semi-surprise, I had intended to push 2.2.1 Windows off to Tuesday night).
Fine with me. I didn't mean the reference to "tonight" as a directive to the release manager, it was what *I* believed, sorry if I was wrong. This is Michael's call.
Cool. Michael has stuck to his release schedule since announcing it, and I see no reason we can't meet it.
On maandag, april 8, 2002, at 11:52 , Guido van Rossum wrote:
+ I believe we're no longer uploading anything to SF, although I'm not sure Michael and Anthony both believe that.
AFAIK they were cc'ed on the msgs where that was decided.
Uhm... Are we talking about uploading releases to sourceforge here? Do I understand that we're not doing this anymore? -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -
On zondag, maart 31, 2002, at 10:39 , Michael Hudson wrote:
April 10 ~1200 GMT: release ends
By now, F, T & J have done their bits, uploaded files to creosote and sf (or pointed me to where I can get them), etc.
Michael, my stuff is done. I've announced it on the pythonmac-sig and given people there 12 hours to find any showstopper bugs, so unless I ask you not to go ahead within twelve hours it's all yours (I understand that we're not doing sf releases anymore, and I don't have access to creosote). The files are in http://www.cwi.nl/ftp/jack/python/mac, you want MacPython221full (both .hqx and .bin) and MacPython221src (both .hqx and .sit). You may also want MacPython221MacOS81patch (.hqx and .sit) which makes this release run on really old MacOS versions. If you are going to put a blurb in your message announcing 2.2.1 there are two fixes in it that are very important to Mac users: - This release finally works on Mac OS X multiprocessors - The IDE is now fully functional on Mac OS X. -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -
participants (6)
-
Fred L. Drake, Jr. -
Guido van Rossum -
Jack Jansen -
Michael Hudson -
Tim Peters -
Tim Peters