chore: update release documentation

README.md

@@ -26,6 +26,13 @@ Other make targets:
 
 ## New Releases
 
+There are a few steps to follow for a new release:
+1. check the application in the staging area according to our test plan
+2. triage all OSV scanner results
+   (visible in CI as `security::osv-scan-container-image`
+    and `security::osv-scan-dependencies` jobs)
+3. bump the release version (see below).
+
 We use `bump-my-version` for releasing new versions.
 
 ```shell
@@ -43,6 +50,10 @@ poetry run bump-my-version show-bump
 poetry run bump-my-version bump major --dry-run --allow-dirty --verbose
 ```
 
+After the changes and the tag created by bump-my-version have been pushed
+the CI will build a new container image and automatically publish the new version
+as a [release in GitLab](https://git.hack-hro.de/rokoli/parcours/-/releases).
+
 ## Deployment
 
 Parcours can be deployed from source and via a container image.