CVS tags, unix Python and MacPython
Things will get worse with the 2.2a2 release, as there are a couple of things that I definitely want in there that aren't finished yet, so it'll be at least another week until I'm done, and moreover I'll have to be making a few (minor) mods to files outside the Mac subtree.
From a procedural, quality-guaranteeing point of view, I think you shouldn't release anything as "MacPython 2.2a2" which does not come from the 2.2a2 tag (and, as Guido explains, you should never move a tag). There is no such thing as the "Unix release" of Python 2.2a2; there is the source distribution, and there happens to be a Windows binary (which I trust came from the tagged source); everything coordinated by the release manager. IOW, if your changes missed the release date by a few days, tough luck - PEP 251 is there precisely for the purpose to align your changes with the rest of the tree, and to enable you to get a consistent, if not perfect, code base included in the alpha release. In theory, all you have to do is to compile this to get a binary distribution, perhaps with any add-on modules that you also want to distribute. It seems that nobody else is making much fuss about this, so I'll shut up now... Regards, Martin
[Martin v. Loewis]
... There is no such thing as the "Unix release" of Python 2.2a2; there is the source distribution, and there happens to be a Windows binary (which I trust came from the tagged source); everything coordinated by the release manager.
In theory, the Windows installer for release I.JAK can be reproduced exactly by checking out the CVS tree tagged for that release. In practice, it also relies on things like the MS runtime DLLs we pack, the expat and zlib and bsddb and Tcl/Tk binaries, and the version of Wise used to build the installer. The release manager hasn't had much to do with that, though, since the last time I was release manager <wink>. Instead the PythonLabs guys all talk about this a lot before a release, and Fred cuts a special HTML-doc snapshot for me (to pack into the Windows installer), and we shoot emails back and forth in private until the Windows (me) and Unix (them) parts are ready to go. Jack doesn't have that kind of intimate access to (and veto power over!) the release process, so there's going to be some kind of compromise somewhere. I think it should be limited to post-release changes in the Mac subtree alone, and that he should tag the whole tree with mac-rIJAK for easy reproducibility later.
... It seems that nobody else is making much fuss about this, so I'll shut up now...
I expect all of us running primarily on Macs gave it top priority <wink>.
Tim Peters writes:
about this a lot before a release, and Fred cuts a special HTML-doc snapshot for me (to pack into the Windows installer), and we shoot emails back and
Sorry to burst your bubble, but those are the released versions. I just make sure you know where it is in time. ;-) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
participants (3)
-
Fred L. Drake, Jr. -
Martin v. Loewis -
Tim Peters