[Python-Dev] Vacation; Python 2.2.3 release. (original) (raw)
Fred L. Drake, Jr. fdrake@acm.org
Thu, 15 May 2003 23:03:11 -0400
- Previous message: [Python-Dev] Vacation; Python 2.2.3 release.
- Next message: [Python-Dev] Vacation; Python 2.2.3 release.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Barry Warsaw writes:
So can we have all the doc changes in place before then, or should we freeze on Wednesday?
We can probably have things done; there's only one big thing that needs to be back-ported in the docs. (I'm pretty sure we solved a fonts problem on the trunk; that fix really needs to be back-ported, but I'll have to spend a little time digging it out. This is really reason to separate the documentation processing tools from the doc tree.)
Normally, the docs distributed with a release candidate are marked as being for the RC in the versioning; I could build both sets of packages ahead of time if we get the CVS tagging right. That would prevent any changes to the docs after the RC, which should be fine. We can deal with the mechanics of that next week, to the extent that anything much needs to happen.
-Fred
-- Fred L. Drake, Jr. PythonLabs at Zope Corporation
- Previous message: [Python-Dev] Vacation; Python 2.2.3 release.
- Next message: [Python-Dev] Vacation; Python 2.2.3 release.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]