Resolve "Patch Release: 2.0.1"
We're releasing patch version
2.0.1 for branch
The MRs to be considered in this update are listed in #202 (closed)
Cherry-pick the listed commits into
CHANGELOG.md: Move appropriate entries into new section
Update version numbers in
[ ] Update
version="unreleased"tags in the default config file XML sources
[ ] Update Sphinx version directives with version
unreleasedin the user docs.
Help on Cherry-Picking
Cherry-picking merge commits requires specifying the "mainline" parent, which
should always be number 1. Append a line indicating a cherry-pick to the commit
message with the
-x argument. The following should do the trick:
git cherry-pick -m 1 -x <commits>
<commits> with the Commit SHAs listed above, separated by a single
whitespace each. Make sure they are in chronological order to reduce the
number of merge conflicts! Fix such conflicts as unintrusively as possible.
Can this MR be merged?
- Pipeline passing
- Delete branch option set
Release issue: #202 (closed)