- - Save the link maps. Currently I keep these on atreus, in
- src/putty-local/maps-<version>.
- rsync -av maps-x86/ atreus:src/putty-local/maps-X.YZ
-
- - Upload the entire release directory to atreus:www/putty/<version>.
- rsync -av putty/ atreus:www/putty/X.YZ
-
- - Do final checks on the release directory in its new location:
- + verify all the signatures:
- for i in `find . -name '*.gpg'`; do case $i in *sums*) gpg --verify $i;; *) gpg --verify $i ${i%%.gpg};; esac; done
- + check the checksum files:
- md5sum -c md5sums
- sha1sum -c sha1sums
- sha256sum -c sha256sums
- sha512sum -c sha512sums
-
- - Having double-checked the release, copy it from atreus to
- chiark:ftp/putty-<ver> and to the:www/putty/<ver>.
- rsync -av putty/ chiark:ftp/putty-X.YZ
- rsync -av putty/ the:www/putty/X.YZ
-
- - Check the permissions! Actually try downloading from the, to make
- sure it really works.
-
- - Update the HTTP redirect at the:www/putty/htaccess which points the
- virtual subdir `latest' at the actual latest release dir. TEST THIS
- ONE - it's quite important.
-
- - Update the FTP symlink (chiark:ftp/putty-latest -> putty-<ver>).
+ - Upload the release itself and its link maps to everywhere it needs
+ to be, by running this in the build.out directory:
+ ../release.pl --version=X.YZ --upload