Doc: CG: minor updates to Releases.

diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi
index ad6a6f79e9fe5e40574349080d7ebc859dc85d05..35e07e595aaac2d071f6fde0dda41eee59fecdd7 100644 (file)
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -120,15 +120,14 @@ make LILYPOND_BRANCH=stable/2.12 lilypond
 @end example
 
 @item Check the regtest comparison in @file{uploads/webtest/} for
-any unintentional breakage.
-
-Note that this test uses the bounding boxes inside lilypond.
-Errors in ghostscript don't generate differences inside lilypond,
-so they are not registered in the regtest comparison.
+any unintentional breakage.  More info in
+@ref{Precompiled regression tests}
 
 @item If any work was done on GUB since the last release, upload
 binaries to a temporary location, ask for feedback, and wait a day
-or two in case there's any major problems.
+or two in case there's any major problems.  Or live dangerously
+and just add a sentence to the release notes.  Or live even more
+dangerously, and don't tell anybody anything.
 
 @end enumerate
 
@@ -172,16 +171,23 @@ git merge release/unstable
 
 @item Update @file{VERSION} in lilypond git and upload changes:
 
-@quotation
-@quotation
+@example
+vi VERSION
+@end example
+
+@itemize
+@item
 VERSION = what you just did +0.0.1
+
+@item
 DEVEL_VERSION = what you just did (i.e. is now online)
-STABLE_VERSION = what's online
-@end quotation
-@end quotation
+
+@item
+STABLE_VERSION = what's online (probably no change here)
+
+@end itemize
 
 @example
-vi VERSION
 git commit -m "Release: bump version." VERSION
 git push origin
 @end example