Merge PR #13591: [rm] update instructions for windows signing

Reviewed-by: Zimmi48

dev/doc/release-process.md

@@ -140,16 +140,16 @@ in time.
 - [ ] Draft a release on GitHub.
 - [ ] Sign the Windows and MacOS packages and upload them on GitHub.
   + The Windows packages must be signed by the Inria IT security service. They
-    should be sent as a link to the binary together with its SHA256 hash in a
-    signed e-mail, via our local contact (currently `@maximedenes`).
-  + The MacOS packages should be signed by our own certificate, by sending them
-    to `@maximedenes`. A detailed step-by-step guide can be found [on the wiki](https://github.com/coq/coq/wiki/SigningReleases).
+    should be sent as a link to the binary (via [filesender](https://filesender.renater.fr) for example)
+    together with its SHA256 hash in a signed e-mail to `dsi.securite` @ `inria.fr`
+    putting `@maximedenes` in carbon copy.
+  + The MacOS packages should be signed with our own certificate. A detailed step-by-step guide can be found [on the wiki](https://github.com/coq/coq/wiki/SigningReleases).
 - [ ] 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)).
-- [ ] Upload the new version of the reference manual to the website.
-  *TODO: setup some continuous deployment for this.*
 - [ ] Merge the website update, publish the release
-  and send announcement e-mails.
+  and send announcement e-mails, typically on
+  the `coq-club@inria.fr` mailing list and the discourse forum
+    ([posting by mail](https://github.com/coq/coq/wiki/Discourse))
 - [ ] Close the milestone
 
 ## At the final release time ##