aboutsummaryrefslogtreecommitdiff
path: root/dev/doc
diff options
context:
space:
mode:
authorEnrico Tassi2020-05-18 18:16:13 +0200
committerGitHub2020-05-18 18:16:13 +0200
commite1e4073f551c34cbaf5b510c3e2eaa11df8b095a (patch)
treee94f0338a9f3b3b582b641ad26edf4c68aa455a2 /dev/doc
parentea6cb6b542e8c356192bb77f234586e0f6d55c8c (diff)
Update release-process.md
Diffstat (limited to 'dev/doc')
-rw-r--r--dev/doc/release-process.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/dev/doc/release-process.md b/dev/doc/release-process.md
index af8a4737be..11f5e90a85 100644
--- a/dev/doc/release-process.md
+++ b/dev/doc/release-process.md
@@ -25,7 +25,9 @@ in time.
the next branch point with the `--release` flag (see next section).
- [ ] Put the corresponding alpha tag using `git tag -s`.
The `VX.X+alpha` tag marks the first commit to be in `master` and not in the
- branch of the previous version.
+ branch of the previous version. Note that you should tag a real commit,
+ not a merge one. After tagging double check that `git describe` picks up
+ the tag you just made (if not, you tagged the wrong commit).
- [ ] Create the `X.X+beta1` milestone if it did not already exist.
- [ ] Decide the release calendar with the team (freeze date, beta date, final
release date) and put this information in the milestone (using the