Updated Release Guidelines (markdown)

Patrick Ziegler 2019-06-28 09:34:11 +02:00
parent 6d5523eef8
commit daa0fde316
1 changed files with 1 additions and 1 deletions

@ -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.