Add Apache alias step.
This commit is contained in:
parent
450ae2ff98
commit
8ac0ce5b74
15
pep-0101.txt
15
pep-0101.txt
|
@ -362,7 +362,8 @@ How to Make A Release
|
|||
directory, You'll move everything in there when the final release
|
||||
comes out.
|
||||
|
||||
___ Move the release .tgz, tar.bz2, and .msi files into place
|
||||
___ Move the release .tgz, tar.bz2, and .msi files into place, as well
|
||||
as the .asc GPG signature files.
|
||||
|
||||
Make sure they are world readable. They should also be group
|
||||
writable, and group-owned by webmaster.
|
||||
|
@ -447,9 +448,6 @@ How to Make A Release
|
|||
___ edit the previous release's last release content.ht page to point to
|
||||
the new release.
|
||||
|
||||
___ Mention the release as the most recent stable one in
|
||||
`doc/faq/general/content.ht` (section "How stable is Python?")
|
||||
|
||||
___ update `doc/content.ht` to indicate the new current documentation
|
||||
version, and remove the current version from any 'in development'
|
||||
section. Update the version in the "What's New" link.
|
||||
|
@ -467,14 +465,10 @@ How to Make A Release
|
|||
|
||||
___ cd to download/releases/X.Y.Z
|
||||
___ Edit the version numbers in content.ht
|
||||
___ Comment out the link to the documentation if this is not a final,
|
||||
___ Comment out the link to the CHM file if this is not a final,
|
||||
remove the comment if it is.
|
||||
___ Copy the new .asc files into place
|
||||
___ Update the md5 checksums
|
||||
|
||||
___ Copy Misc/NEWS to download/releases/X.Y.Z/NEWS.txt
|
||||
___ Copy Lib/idlelib/NEWS.txt to download/releases/X.Y.Z/IDLENEWS.txt
|
||||
|
||||
Note, you don't have to copy the actual .tgz or tar.bz2 tarballs into
|
||||
this directory because they only live on dinsdale in the ftp directory.
|
||||
|
||||
|
@ -482,6 +476,9 @@ How to Make A Release
|
|||
will trigger the live site to update itself, and at that point the
|
||||
release is live.
|
||||
|
||||
___ If this is a final release, create a new python.org/X.Y Apache alias
|
||||
(or ask pydotorg to do so for you).
|
||||
|
||||
Now it's time to write the announcement for the mailing lists. This is the
|
||||
fuzzy bit because not much can be automated. You can use an earlier
|
||||
announcement as a template, but edit it for content!
|
||||
|
|
Loading…
Reference in New Issue