- - 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>).
-
- - Check the Docs page links correctly to the release docs. (It
- should do this automatically, owing to the `latest' HTTP
- redirect.)
-
- - Check that the web server attaches the right content type to .HLP,
- .CNT and .CHM files, by downloading one of each and checking
- they're all application/octet-stream.
- for ext in hlp cnt chm; do curl -v http://the.earth.li/~sgtatham/putty/X.YZ/putty.$ext 2>&1 >/dev/null | grep Content-Type; done
-
- - Run 'git push' in the website checkout, and then 'git pull' in
- ~/www/putty on atreus to fetch the website updates.
-
- - Push the changes to PuTTY itself. Something like:
- git push origin master # update the master branch
- git push origin --tags # should push the new release tag
- git push origin :pre-0.XX # delete the pre-release branch
-
- - Run 'git push' in the putty-wishlist checkout. Then run 'git pull'
- in ~/pub/putty-wishlist on atreus, and update the wishlist web
- pages with the commands
- cd ~/pub/putty-wishlist/control
- perl bugs2html
-
- - Check over the web site to make sure all the changes to wishlist
- and main web pages are present and correct.
+ - 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
+
+ - Check that downloads via version-numbered URLs all work:
+ ../release.pl --version=X.YZ --precheck
+
+ - Switch the 'latest' links over to the new release:
+ * Update the HTTP redirect at the:www/putty/htaccess .
+ * Update the FTP symlink at chiark:ftp/putty-latest .
+
+ - Now verify that downloads via the 'latest' URLs are all redirected
+ correctly and work:
+ ../release.pl --version=X.YZ --postcheck
+
+ - Push all the git repositories:
+ * run 'git push' in the website checkout
+ * run 'git push' in the wishlist checkout
+ * push from the main PuTTY checkout. Typically this one will be
+ pushing both the release tag and an update to the master branch,
+ plus removing the pre-release branch, so you'll want some
+ commands along these lines:
+ git push origin master # update the master branch
+ git push origin --tags # should push the new release tag
+ git push origin :pre-0.XX # delete the pre-release branch
+
+ - Run ~/adm/puttyweb.sh on atreus to update the website after all
+ those git pushes.
+
+ - Check that the unpublished website on atreus looks sensible.