From daa0fde316a642a55fdb7f3d60b2577f7bae3711 Mon Sep 17 00:00:00 2001 From: Patrick Ziegler Date: Fri, 28 Jun 2019 09:34:11 +0200 Subject: [PATCH] Updated Release Guidelines (markdown) --- Release-Guidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Release-Guidelines.md b/Release-Guidelines.md index 4bc6052..06a548f 100644 --- a/Release-Guidelines.md +++ b/Release-Guidelines.md @@ -39,7 +39,7 @@ Patch releases should be done only every few bug fixes as to reduce the overhead As already mentioned, every release needs to be preceded by a release PR which updates the version numbers and gives some explanation as to why a release is needed. The release PR needs to update the version number in: -* The `GIT_TAG` and `GIT_TAG_NAMESPACE` macro in `include/version.hpp` +* `version.txt` After it is reviewed, the release PR is squashed and the changelog for the new version is copied into the commit message body. **Note:** For patch releases the release PR also contains the bug fix commits, so it is not squashed.