From 5f675c0e657abe01e3b48e0522e070397a576c54 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20M=C3=A4der?= Date: Tue, 27 Apr 2021 09:31:36 +0200 Subject: [PATCH] Updated Release (markdown) --- Release.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Release.md b/Release.md index 8001b95..59ce252 100644 --- a/Release.md +++ b/Release.md @@ -21,7 +21,13 @@ Now another maintainer has to approve the PR. ## Make the release (mostly automatically) -Run `./release.sh` in the `develop` branch. +The release script automates the merging and tagging and pushing. +It tried to be as safe as possible to use. +E.g. it checks that there are no pending changes in the current repository. + +1. Run `./release.sh` in the `develop` branch. +2. Now go to Github and [draft a new release][draft]. Copy the text from [the most recent previous release][latest] and adjust it according to the new release. +3. Eventually announce the release [on our Slack channel][slack]. ## Make the release (completely manually)