PEP 101: doc archives are now built for rcs
This commit is contained in:
parent
88131a0fe2
commit
dd1e7667cc
|
@ -425,14 +425,14 @@ How to Make A Release
|
|||
|
||||
___ Use ``gpg --verify`` to make sure they got uploaded intact.
|
||||
|
||||
___ If this is a final release: Move the doc zips and tarballs to
|
||||
___ If this is a final or rc release: Move the doc zips and tarballs to
|
||||
/srv/www.python.org/ftp/python/doc/X.Y.Z, creating the directory
|
||||
if necessary, and adapt the "current" symlink in .../doc to point to
|
||||
that directory. Note though that if you're releasing a maintenance
|
||||
release for an older version, don't change the current link.
|
||||
|
||||
___ If this is a final release (even a maintenance release), also
|
||||
unpack the HTML docs to /srv/docs.python.org/release/X.Y.Z on
|
||||
___ If this is a final or rc release (even a maintenance release), also
|
||||
unpack the HTML docs to /srv/docs.python.org/release/X.Y.Z[rcA] on
|
||||
docs.iad1.psf.io. Make sure the files are in group "docs" and are
|
||||
group-writeable. If it is a release of a security-fix-only version,
|
||||
tell the DE to build a version with the "version switcher"
|
||||
|
|
Loading…
Reference in New Issue