aboutsummaryrefslogtreecommitdiff
path: root/dev/doc
diff options
context:
space:
mode:
Diffstat (limited to 'dev/doc')
-rw-r--r--dev/doc/changes.md2
-rw-r--r--dev/doc/release-process.md7
2 files changed, 7 insertions, 2 deletions
diff --git a/dev/doc/changes.md b/dev/doc/changes.md
index 9498ab8bbb..ae4c6328b5 100644
--- a/dev/doc/changes.md
+++ b/dev/doc/changes.md
@@ -1,3 +1,5 @@
+## Changes between Coq 8.12 and Coq 8.13
+
## Changes between Coq 8.11 and Coq 8.12
### Code formatting
diff --git a/dev/doc/release-process.md b/dev/doc/release-process.md
index 340b66bbd0..da9f37f666 100644
--- a/dev/doc/release-process.md
+++ b/dev/doc/release-process.md
@@ -8,7 +8,7 @@ early enough in the process for this person to be known at that point
in time.
- [ ] Create a new issue to track the release process where you can copy-paste
- the present checklist.
+ the present checklist from `dev/doc/release-process.md`.
- [ ] Change the version name to the next major version and the magic
numbers (see [#7008](https://github.com/coq/coq/pull/7008/files)).
@@ -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