- Write a release announcement (basically a summary of the changes
since the last release). Squirrel it away in
- atreus:src/putty-local/announce-<ver> in case it's needed again
+ thyestes:src/putty-local/announce-<ver> in case it's needed again
within days of the release going out.
- Update the website, in a local checkout:
git push origin --tags # should push the new release tag
git push origin :pre-X.YZ # delete the pre-release branch
- - Run ~/adm/puttyweb.sh on atreus to update the website after all
+ - Run ~/adm/puttyweb.sh on thyestes to update the website after all
those git pushes.
- - Check that the unpublished website on atreus looks sensible.
+ - Check that the unpublished website on thyestes looks sensible.
- - Run webupdate, so that all the changes on atreus propagate to
+ - Run webupdate, so that all the changes on thyestes propagate to
chiark. Important to do this _before_ announcing that the release
is available.
-d "putty" or die "no putty directory in cwd";
0 == system("rsync", "-av", "maps/",
- "atreus:src/putty-local/maps-$version")
+ "thyestes:src/putty-local/maps-$version")
or die "could not upload link maps";
- for my $location (["atreus", "www/putty/$version"],
- ["the", "www/putty/$version"],
- ["chiark", "ftp/putty-$version"]) {
+ for my $location (["thyestes", "www/putty/$version"],
+ ["the", "www/putty/$version"],
+ ["chiark", "ftp/putty-$version"]) {
my ($host, $path) = @$location;
0 == system("rsync", "-av", "putty/", "$host:$path")
or die "could not upload release to $host";