From f7370a7cdcb1eeec05b966a0c9552dc8dd200287 Mon Sep 17 00:00:00 2001 From: Ramon Wenger Date: Mon, 1 Mar 2021 16:23:20 +0100 Subject: [PATCH] Update readme --- README.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 09fc45dc..174efafa 100644 --- a/README.md +++ b/README.md @@ -181,7 +181,7 @@ The current master will always be deployed in the evening, if there are new comm Whenever you do a new release, please tag the current commit after merging with the current date: - git tag -a release/v2019-09-10 + git tag -a v2019-09-10 `git tag -a` creates an annotated tag, which must have a release message (like a commit message). For now, just repeat the current date, like: @@ -189,12 +189,22 @@ Whenever you do a new release, please tag the current commit after merging with You can and should then push the tag to the repo - git push origin release/v2019-09-10 + git push origin v2019-09-10 You can later see the metadata of the tag with git show release/v2019-09-10 +or + + git tag -ln + +NB: If there are two releases on the same day, use the pattern `v2020-03-01.x` eg. `v2020-03-01.1` for the subsequent releases + +#### Hotfixes + +Please use the pattern `v2020-03-01.hotfix` for hotfix releases + ## Testing