Update releasing documentation with version name

Author: sim642

docs/developer-guide/releasing.md

@@ -2,38 +2,41 @@
 
 ## opam
 
-1. Update list of authors and contributors in `.zenodo.json`, `CITATION.cff` and `dune-project`.
-2. Update `CHANGELOG.md`:
+1. Choose version name (collaboratively).
+2. Update list of authors and contributors in `.zenodo.json`, `CITATION.cff` and `dune-project`.
+3. Update `CHANGELOG.md`:
 
-    1. Add a desired version number (`vX.Y.Z`) header at the top.
+    1. Add a desired version number (`vX.Y.Z`) and name header at the top.
     2. Add a list of biggest changes compared to the previous version.
 
-3. Install dune-release: `opam install dune-release`.
 4. Remove all opam pins because _opam-repository doesn't allow them_.
 
     * If the pinned changes have been released and published in opam, remove the pin (and add a version lower bound).
     * If the pinned changes are not strictly necessary for building (but just optimization or stability), then temporarily remove the pin.
 
-5. Regenerate `goblint.opam`: `dune build`.
-6. Regenerate `goblint.opam.locked`: `opam pin add goblint.dev . --no-action` and `opam lock .`.
+5. Check opam file for previous release on opam-repository for changes.
+6. Regenerate `goblint.opam`: `dune build`.
+7. Regenerate `goblint.opam.locked`: `opam pin add goblint.dev . --no-action` and `opam lock .`.
 
     Pinning the package is necessary for locking, otherwise lockfile will be generated for previously published version.
     Manually remove not installed `depopts` from `conflicts`.
 
-7. Check with `dune-release check`.
+8. Install dune-release: `opam install dune-release`.
+
+9. Check with `dune-release check`.
 
     All changes must be committed because the working tree is not checked.
 
     The warning `[FAIL] opam field doc cannot be parsed by dune-release` is fine and can be ignored (see <https://github.com/ocamllabs/dune-release/issues/154>).
 
-8. Check that "unlocked" workflow passes on GitHub Actions.
+10. Check that "unlocked" workflow passes on GitHub Actions.
 
     It can be run manually on the release branch for checking.
 
-9. Tag the release: `dune-release tag`.
-10. Create the distribution archive: `dune-release distrib`.
+11. Tag the release: `dune-release tag`.
+12. Create the distribution archive: `dune-release distrib`.
 
-11. Check created _distribution archive_ (in `_build`) in a clean environment:
+13. Check created _distribution archive_ (in `_build`) in a clean environment:
 
     1. Pull Docker image: `docker pull ocaml/opam:ubuntu-22.04-ocaml-4.14` (or newer).
     2. Extract distribution archive.
@@ -46,21 +49,22 @@
     9. Check that analysis works: `goblint -v tests/regression/04-mutex/01-simple_rc.c`.
     10. Exit Docker container.
 
-12. Temporarily enable Zenodo GitHub webhook.
+14. Temporarily enable Zenodo GitHub webhook.
 
     This is because we only want numbered version releases to automatically add a new version to our Zenodo artifact.
     Other tags (like SV-COMP or paper artifacts) have manually created Zenodo artifacts anyway and thus shouldn't add new versions to the main Zenodo artifact.
 
-13. Create a GitHub release with the git tag: `DUNE_RELEASE_DELEGATE=github-dune-release-delegate dune-release publish distrib`.
+15. Create a GitHub release with the git tag: `DUNE_RELEASE_DELEGATE=github-dune-release-delegate dune-release publish distrib`.
 
     Explicitly specify `distrib` because we don't want to publish OCaml API docs.
     Environment variable workaround for the package having a Read the Docs `doc` URL (see <https://github.com/ocamllabs/dune-release/issues/154>).
 
-14. Re-disable Zenodo GitHub webhook.
+16. Re-disable Zenodo GitHub webhook.
 
-15. Create an opam package: `dune-release opam pkg`.
-16. Submit the opam package to opam-repository: `dune-release opam submit`.
-17. Revert temporary removal of opam pins.
+17. Edit GitHub release to add version name.
+18. Create an opam package: `dune-release opam pkg`.
+19. Submit the opam package to opam-repository: `dune-release opam submit`.
+20. Revert temporary removal of opam pins.
 
 
 ## SV-COMP