Update release instructions

Author: thijskh

make_release.sh

@@ -58,6 +58,9 @@ cd "$OWD"
 mv $TEMPDIR/domjudge-$VERSION.tar.gz .
 rm -rf "$TEMPDIR"
 
+sha256sum domjudge-$VERSION.tar.gz > domjudge-$VERSION.tar.gz.sha256sum
+gpg -a --detach-sign --digest-algo SHA256 domjudge-$VERSION.tar.gz
+
 echo "Release file: 'domjudge-$VERSION.tar.gz'"
 echo "ChangeLog version: '$CHLOG'"
 

new_release_howto.txt

@@ -20,19 +20,18 @@ on the account `domjudge@vm-domjudge`):
     The tarball is placed in the current dir; check that it looks correct,
     test e.g. by unpacking it and running
         ./configure && make build
+ 1. If releasing from the master branch, create a new version branch:
+        git checkout -b x.y
+        git push --set-upstream origin x.y
+        git checkout master
  1. Update files above to `{version+1}DEV`, `DEBUG=1`, and commit.
- 1. Generate sha256sum and GPG signature:
-        sha256sum domjudge-$TAG.tar.gz > domjudge-$TAG.tar.gz.sha256sum
-        gpg -a --detach-sign --digest-algo SHA256 domjudge-$TAG.tar.gz
-    Copy these files to `/srv/http/domjudge/releases/`
+ 1. Copy domjudge-$TAG.tar.gz* to `/srv/http/domjudge/releases/`
  1. Update the DOMjudge homepage: commit changes in the `domjudge-scripts`
     repository under `website/` and run `make install` as domjudge@domjudge
  1. If this is a new major or minor version, update the release documentation
     under `/srv/http/domjudge/docs/manual` by adding a new version to the
     file `versions.json` and updating the redirect destination in `index.html`.
     The documentation is regenerated once every hour.
- 1. If necessary, add a source package of included dash static shell in
-    `/srv/http/domjudge/sources/`.
  1. Bump the docker containers and build Debian packages (or make someone
     do this).
  1. Send an email to [email protected].