[Python-Dev] 2.2.1 release mechanics (original) (raw)

Michael Hudson mwh@python.net
31 Mar 2002 21:39:24 +0100

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