aboutsummaryrefslogtreecommitdiff
path: root/dev
diff options
context:
space:
mode:
authorEmilio Jesus Gallego Arias2020-05-19 14:23:01 +0200
committerEmilio Jesus Gallego Arias2020-05-19 14:23:01 +0200
commit5b23b80c8a0af603e8078616b2c5957a6f709e62 (patch)
tree844254f70ec90c801eda8c1f95d605c747fae261 /dev
parent407ca661d7eb33afed706afe74f11fccac2f1dd4 (diff)
parentffe1de0bab363902f3e9c517345713f74cfa3071 (diff)
Merge PR #12353: Update release-process.md
Reviewed-by: ejgallego
Diffstat (limited to 'dev')
-rw-r--r--dev/doc/release-process.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/dev/doc/release-process.md b/dev/doc/release-process.md
index af8a4737be..da9f37f666 100644
--- a/dev/doc/release-process.md
+++ b/dev/doc/release-process.md
@@ -25,7 +25,10 @@ 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 this commit is the first commit
+ in the first PR merged in master, not the merge commit for that PR.
+ 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