Update minor release checklist with new news instructions

[lilypond.git] / Documentation / contributor / release-work.itexi

diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi
index 8227763e40d08f819ede3f958451a49aba6c6736..32b7a1ac71efb022a0bcfa9044fda23edac8e23b 100644 (file)
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -74,6 +74,10 @@ A @qq{minor release} means an update of @code{y} in @code{2.x.y}.
 
 @enumerate
 
+@item
+Don't forget to prepare the GUB build machine by deleting and moving unneeded
+files: see @qq{Subsequent builds} in @ref{Notes on builds with GUB}.
+
 @item
 Using any system with git pull access (not necessarily the GUB
 build machine), use the commands below to do the following:
@@ -104,7 +108,7 @@ VERSION_STABLE = the current stable version (probably no change here)
 @end itemize
 
 @item
-update the @qq{Welcome to Lilypond} version numbers to the version about to be
+update the @qq{Welcome to LilyPond} version numbers to the version about to be
 released
 
 @end itemize
@@ -128,17 +132,35 @@ git merge origin/master
 make -C $LILYPOND_BUILD_DIR po-replace
 mv $LILYPOND_BUILD_DIR/po/lilypond.pot po/
 gedit Documentation/web/news-front.itexi Documentation/web/news.itexi
+gedit Documentation/web/news-headlines.itexi
 gedit VERSION
 gedit ly/Wel*.ly
 @end example
 
+Editing the @file{news-headlines.itexi} file is a bit tricky, since it contains
+URLs with escaped characters.  An example of what is needed is that releasing
+@code{2.19.50} after the release of @code{2.19.49} needed the line:
+
+@example
+@@uref@{news.html#LilyPond-2_002e19_002e49-released-October-16_002c-2016,
+  LilyPond 2.19.49 released - @@emph@{October 16, 2016@}@}
+@end example
+
+to be changed to:
+
+@example
+@@uref@{news.html#LilyPond-2_002e19_002e50-released-November-6_002c-2016,
+  LilyPond 2.19.50 released - @@emph@{November 6, 2016@}@}
+@end example
+
+Don't forget to update the entry above that line to show the latest release
+version.
+
 @item
 Commit, push, switch back to master (or wherever else):
 
 @example
 git commit -m "Release: bump VERSION_DEVEL." VERSION
-git commit -m "Release: bump VERSION_DEVEL." ly/Welcome_to_LilyPond.ly
-git commit -m "Release: bump VERSION_DEVEL." ly/Welcome-to-LilyPond-MacOS.ly
 git commit -m "PO: update template." po/lilypond.pot
 git commit -m "Release: update news." Documentation/web/
 git commit -m "Release: bump Welcome versions." ly/Wel*.ly
@@ -586,7 +608,7 @@ to continue uninterrupted.
 Download GUB and start the set up:
 
 @example
-git clone git://github.com/gperciva/gub/gub.git
+git clone git://github.com/gperciva/gub.git
 cd gub
 make bootstrap
 @end example
@@ -610,11 +632,11 @@ Download the test output from lilypond.org (you will need to
 replace @code{2.15.33-1} with the latest build):
 
 @smallexample
-@uref{http://lilypond.org/download/binaries/test-output/lilypond-2.15.33-1.test-output.tar.bz2}
+@uref{http://lilypond.org/downloads/binaries/test-output/lilypond-2.15.33-1.test-output.tar.bz2}
 @end smallexample
 
-Copy the tarball into @file{gub/regtests/}, and tell the build
-system that you have done this:
+Copy the tarball into @file{regtests/}, and tell the build system that
+you have done this:
 
 @example
 touch regtests/ignore