From 52dc2c57acc7cae845f1378371ae669f9f8fb65e Mon Sep 17 00:00:00 2001 From: Benjamin Peterson Date: Mon, 24 Nov 2014 20:08:44 -0600 Subject: [PATCH] dl-files has a new hostname --- pep-0101.txt | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/pep-0101.txt b/pep-0101.txt index 7b21d4828..55b43d0c2 100644 --- a/pep-0101.txt +++ b/pep-0101.txt @@ -35,7 +35,7 @@ Things You'll Need which hopefully will be on the "web of trust" with at least one of the other release managers. - * Access to ``dl-files.psf.io``, the server that hosts download files. + * Access to ``dl-files.iad1.psf.io``, the server that hosts download files. You'll be uploading files directly here. * Shell access to ``hg.python.org``, the Python Mercurial host. You'll @@ -335,11 +335,11 @@ How to Make A Release - Now he runs msi.py with ActivePython or Python with pywin32. The WE checksums the files (*.msi, *.chm, *-pdb.zip), uploads them to - dl-files.psf.io together with gpg signature files, and emails you the + dl-files.iad1.psf.io together with gpg signature files, and emails you the location and md5sums. - ___ The ME builds Mac installer packages and uploads them to dl-files.psf.io - together with gpg signature files. + ___ The ME builds Mac installer packages and uploads them to + dl-files.iad1.psf.io together with gpg signature files. ___ Time to build the source tarball. Be sure to update your clone to the correct branch. E.g. @@ -367,7 +367,7 @@ How to Make A Release tarballs and signatures in a subdirectory called 'X.Y.ZaN/src', and the built docs in 'X.Y.ZaN/docs' (for final releases). - ___ scp or rsync all the files to your home directory on dl-files.psf.io. + ___ scp or rsync all the files to your home directory on dl-files.iad1.psf.io. 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 @@ -401,13 +401,13 @@ How to Make A Release freshly unpacked directory looks weird, you better stop now and figure out what the problem is. - ___ 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 + ___ Now you need to go to dl-files.iad1.psf.io and move all the files in place + over there. Our policy is that every Python version gets its own directory, but each directory contains all releases of that version. - ___ On dl-files.psf.io, cd /srv/www.python.org/ftp/python/X.Y.Z creating - it if necessary. Make sure it is owned by group 'downloads' and - group-writable. + ___ On dl-files.iad1.psf.io, cd /srv/www.python.org/ftp/python/X.Y.Z + creating it if necessary. Make sure it is owned by group 'downloads' + and group-writable. ___ 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 @@ -498,7 +498,7 @@ How to Make A Release production release" paragraph as appropriate Note, you don't have to copy any release files into this directory; - they only live on dl-files.psf.io in the ftp directory. + they only live on dl-files.iad1.psf.io in the ftp directory. ___ Edit `download/releases/content.ht` to update the version numbers for this release. There are a bunch of places you need to touch: