From 861e3ed8b0c96354c959767ae4750e28193f8d38 Mon Sep 17 00:00:00 2001
From: Théo Zimmermann
Date: Sat, 25 Jan 2020 00:00:06 +0100
Subject: Publishing a new version on Zenodo: not a relevant step for beta
 versions.

Also, stop pinging when copying checklist to new issue.
---
 dev/doc/release-process.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

(limited to 'dev/doc')

diff --git a/dev/doc/release-process.md b/dev/doc/release-process.md
index ba68501e04..2b09b2b42e 100644
--- a/dev/doc/release-process.md
+++ b/dev/doc/release-process.md
@@ -127,11 +127,11 @@ in time.
 - [ ] Send an e-mail on Coqdev announcing that the tag has been put so that
   package managers can start preparing package updates (including a
   `coq-bignums` compatible version).
-- [ ] Ping **@erikmd** to update the Docker images in `coqorg/coq`
+- [ ] Ping `@erikmd` to update the Docker images in `coqorg/coq`
   (requires `coq-bignums` in `extra-dev` for a beta / in `released`
   for a final release).
 - [ ] Draft a release on GitHub.
-- [ ] Get **@maximedenes** to sign the Windows and MacOS packages and
+- [ ] Get `@maximedenes` to sign the Windows and MacOS packages and
   upload them on GitHub.
 - [ ] Prepare a page of news on the website with the link to the GitHub release
   (see [coq/www#63](https://github.com/coq/www/pull/63)).
@@ -139,8 +139,6 @@ in time.
   *TODO: setup some continuous deployment for this.*
 - [ ] Merge the website update, publish the release
   and send announcement e-mails.
-- [ ] Ping **@Zimmi48** to publish a new version on Zenodo.
-  *TODO: automate this.*
 - [ ] Close the milestone
 
 ## At the final release time ##
@@ -160,7 +158,10 @@ in time.
 
 Repeat the generic process documented above for all releases.
 
+Ping `@Zimmi48` to:
+
 - [ ] Switch the default version of the reference manual on the website.
+- [ ] Publish a new version on Zenodo.
 
 ## At the patch-level release time ##
 
-- 
cgit v1.2.3