[Python-Dev] Re: Stability and change (original) (raw)
Fred L. Drake, Jr. fdrake@acm.org
Mon, 8 Apr 2002 12:23:39 -0400
- Previous message: [Python-Dev] Re: Stability and change
- Next message: [Python-Dev] Re: Stability and change
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Skip Montanaro writes:
I don't know. I see a lot more version-related checkins than that float by just before a release. What about the docs for example?
The docs generate at least two of these:
Doc/Makefile
Doc/texinputs/boilerplate.tex
The Makefile case probably can't be automated, since it changes to add a "patchlevel" of it's own when the release is done separately from a Python release (such as the 2.2p1 doc release). We've traditionally also "hard-coded" the release date into the source boilerplate.tex, so that formatting the released doc sources doesn't generate a new date. (Switching CVS back to \today afterward generates yet another checkin.)
There's probably a better way to handle this -- I don't like all the dance steps we have to do for this either!
-Fred
-- Fred L. Drake, Jr. PythonLabs at Zope Corporation
- Previous message: [Python-Dev] Re: Stability and change
- Next message: [Python-Dev] Re: Stability and change
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]