updates for downloads move

This commit is contained in:
Benjamin Peterson 2014-08-30 17:25:09 -04:00
parent c7657405ff
commit 3725d5f124
1 changed files with 15 additions and 15 deletions

View File

@ -35,8 +35,8 @@ Things You'll Need
which hopefully will be on the "web of trust" with at least one of which hopefully will be on the "web of trust" with at least one of
the other release managers. the other release managers.
* Access to ``dinsdale.python.org``, the Python web host. You'll * Access to ``dl-files.psf.io``, the server that hosts download files.
be uploading files directly here. You'll be uploading files directly here.
* Shell access to ``hg.python.org``, the Python Mercurial host. You'll * Shell access to ``hg.python.org``, the Python Mercurial host. You'll
have to adapt repository configuration there. have to adapt repository configuration there.
@ -335,11 +335,11 @@ How to Make A Release
- Now he runs msi.py with ActivePython or Python with pywin32. - Now he runs msi.py with ActivePython or Python with pywin32.
The WE checksums the files (*.msi, *.chm, *-pdb.zip), uploads them to The WE checksums the files (*.msi, *.chm, *-pdb.zip), uploads them to
dinsdale together with gpg signature files, and emails you the location dl-files.psf.io together with gpg signature files, and emails you the
and md5sums. location and md5sums.
___ The ME builds Mac installer packages and uploads them to dinsdale together ___ The ME builds Mac installer packages and uploads them to dl-files.psf.io
with gpg signature files. together with gpg signature files.
___ Time to build the source tarball. Be sure to update your clone to the ___ Time to build the source tarball. Be sure to update your clone to the
correct branch. E.g. correct branch. E.g.
@ -364,7 +364,7 @@ How to Make A Release
tarballs and signatures in a subdirectory called 'X.Y.ZaN/src', and the tarballs and signatures in a subdirectory called 'X.Y.ZaN/src', and the
built docs in 'X.Y.ZaN/docs' (for final releases). built docs in 'X.Y.ZaN/docs' (for final releases).
___ scp or rsync all the files to your home directory on dinsdale.python.org. ___ scp or rsync all the files to your home directory on dl-files.psf.io.
While you're waiting for the files to finish uploading, you can continue While you're waiting for the files to finish uploading, you can continue
on with the remaining tasks. You can also ask folks on #python-dev on with the remaining tasks. You can also ask folks on #python-dev
@ -401,32 +401,32 @@ How to Make A Release
freshly unpacked directory looks weird, you better stop now and freshly unpacked directory looks weird, you better stop now and
figure out what the problem is. figure out what the problem is.
___ Now you need to go to dinsdale.python.org and move all the files in ___ Now you need to go to dl-files.psf.io and move all the files in
place over there. Our policy is that every Python version gets its own place over there. Our policy is that every Python version gets its own
directory, but each directory contains all releases of that version. directory, but each directory contains all releases of that version.
___ On dinsdale, cd /data/ftp.python.org/pub/python/X.Y.Z ___ On dl-files.psf.io, cd /srv/www.python.org/ftp/python/X.Y.Z creating
creating it if necessary. Make sure it is owned by group 'webmaster' it if necessary. Make sure it is owned by group 'downloads' and
and group-writable. group-writable.
___ Move the release .tgz, and .tar.xz files into place, as well as the ___ Move the release .tgz, and .tar.xz files into place, as well as the
.asc GPG signature files. The Win/Mac binaries are usually put there .asc GPG signature files. The Win/Mac binaries are usually put there
by the experts themselves. by the experts themselves.
Make sure they are world readable. They should also be group Make sure they are world readable. They should also be group
writable, and group-owned by webmaster. writable, and group-owned by downloads.
___ Use `gpg --verify` to make sure they got uploaded intact. ___ 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 release: Move the doc zips and tarballs to
/data/ftp.python.org/pub/python/doc/X.Y.Z creating the directory /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 if necessary, and adapt the "current" symlink in .../doc to point to
that directory. Note though that if you're releasing a maintenance that directory. Note though that if you're releasing a maintenance
release for an older version, don't change the current link. release for an older version, don't change the current link.
___ If this is a final release (even a maintenance release), also unpack ___ If this is a final release (even a maintenance release), also unpack
the HTML docs to the HTML docs to
/data/ftp.python.org/pub/docs.python.org/release/X.Y.Z. /data/ftp.python.org/pub/docs.python.org/release/X.Y.Z on dinsdale.
If it is a release of a security-fix-only version, tell the DE to If it is a release of a security-fix-only version, tell the DE to
build a version with the "version switcher" and put it there. build a version with the "version switcher" and put it there.
@ -492,7 +492,7 @@ How to Make A Release
production release" paragraph as appropriate production release" paragraph as appropriate
Note, you don't have to copy any release files into this directory; Note, you don't have to copy any release files into this directory;
they only live on dinsdale in the ftp directory. they only live on dl-files.psf.io in the ftp directory.
___ Edit `download/releases/content.ht` to update the version numbers for ___ Edit `download/releases/content.ht` to update the version numbers for
this release. There are a bunch of places you need to touch: this release. There are a bunch of places you need to touch: