[Python-Dev] CVS tags, unix Python and MacPython

[Tim Peters]

[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>.