01/02: doc: Update release instructions.

[Ludovic Court�s]

civodul pushed a commit to branch master
in repository maintenance.

commit a719036099a8dc08f9e439b01275d9a48521b878
Author: Ludovic Courtès <address@hidden>
AuthorDate: Wed Apr 15 19:11:16 2020 +0200

    doc: Update release instructions.
    
    * doc/release.org (Add a Git tag): Mention release candidates.
    (Add a Cuirass jobset for branch 'version-X.Y.Z'): Mention Cuirass.
    (Update web pages): Adjust for the new web site infrastructure.
    (Update the on-line copy of the manual): Update.
---
 doc/release.org | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

diff --git a/doc/release.org b/doc/release.org
index aa9d633..7d88f6d 100644
--- a/doc/release.org
+++ b/doc/release.org
@@ -38,13 +38,15 @@ your maintenance.git checkout.  Make sure to commit it:
 
 Create a signed Git tag, like this:
 
-  $ git tag -s -u MY-KEY -m "GNU Guix X.Y." vX.Y
+  $ git tag -s -u MY-KEY -m "GNU Guix X.YrcZ." vX.YrcZ
   $ autoreconf  # to update $(PACKAGE_VERSION)
 
+Use “rcZ” for release candidates, drop it otherwise.
+
 The tag must be `vX.Y'.  For the sake of consistency, always use
 "GNU Guix X.Y." as the tag comment.
 
-** Run “make release”
+** Run “make release” for one or several release candidates
 
 This will automatically build:
 
@@ -86,7 +88,7 @@ Make sure to publish your public key on public OpenPGP servers
 (keys.gnupg.net, pgp.mit.edu, etc.), so that people can actually use it
 to check the authenticity and integrity of the tarball.
 
-** Add a Hydra jobset for branch 'version-X.Y.Z'
+** Add a Cuirass jobset for branch 'version-X.Y.Z'
 
 This jobset will have to be kept until the next release, so that
 substitutes remain available.
@@ -97,18 +99,15 @@ First, re-read the GNU Maintainers Guide 
[[info:maintain.info#Announcements][on
 
 ** Update web pages
 
-  - Update the ‘latest-guix-version’ value in (www shared), in the
-    guix-artwork.git repository.
-  - Regenerate the web site by using (export-web-site
-    "/path/to/cvs/checkout") from the (www) module, and then “cvs ci”
-    the result so that gnu.org is actually updated.
+Update the ‘latest-guix-version’ value in (apps base utils), in the
+guix-artwork.git repository.  Add a blog post under posts/.
 
-** Update the on-line copy of the manual
+The web site will be automatically rebuilt by an mcron job on berlin.
 
-Use Gnulib's `gendocs' script, add to the manual/ directory of the web site.
+** Update the on-line copy of the manual
 
-  $ cd doc
-  $ ~/src/gnulib/build-aux/gendocs.sh guix "GNU Guix X.Y Reference Manual"
+Change the ‘static-web-site’ service in hydra/berlin.scm
+(guix-maintenance.git) so that it builds the ‘version-X.Y.Z’ branch.
 
 ** Prepare the email announcement