Web build: update src dir.

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

diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi
index 608e1859f49f21cd5053eb8967b886f3f838a4f7..146fcc45b788f0ff4b33be4bb555f05844f9125b 100644 (file)
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -84,12 +84,18 @@ A @qq{minor release} means an update of @code{y} in @code{2.x.y}.
 
 @item
 Switch to the release branch, get changes, prep release
-announcement, upload:
+announcement:
 
 @example
 git checkout release/unstable
 git merge origin
 vi Documentation/web/news-front.itexi Documentation/web/news.itexi
+@end example
+
+@item
+Commit, push, switch back to master:
+
+@example
 git commit -m "Release: update news." Documentation/web/
 git push origin
 @end example
@@ -117,6 +123,10 @@ make LILYPOND_BRANCH=stable/2.12 lilypond
 @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.
+
 @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.
@@ -137,7 +147,7 @@ from the rsync command in @file{test-lily/rsync-lily-doc.py} and
 @item Upload GUB by running:
 
 @example
-make lilypond-upload LILYPOND_BRANCH=master LILYPOND_REPO_URL=git://git.sv.gnu.org/lilypond.git
+make lilypond-upload LILYPOND_BRANCH=release/unstable LILYPOND_REPO_URL=git://git.sv.gnu.org/lilypond.git
 @end example
 
 @noindent
@@ -161,15 +171,22 @@ git checkout master
 git merge release/unstable
 @end example
 
-@item Update @file{VERSION} in lilypond git:
+@item Update @file{VERSION} in lilypond git and upload changes:
 
-@example
+@quotation
+@quotation
 VERSION = what you just did +0.0.1
 DEVEL_VERSION = what you just did (i.e. is now online)
 STABLE_VERSION = what's online
+@end quotation
+@end quotation
+
+@example
+vi VERSION
+git commit -m "Release: bump version." VERSION
+git push origin
 @end example
 
-@item Push changes.
 
 @item (for now) do a @code{make doc} and manually upload:
 
@@ -199,6 +216,9 @@ rsync -a $EXAMPLES graham@@lilypond.org:media/ly-examples
 
 A @qq{major release} means an update of @code{x} in @code{2.x.0}.
 
+- happens when we have 0 Critical issues for two weeks (14 days).
+
+
 Before release:
 
 * write release notes. note: stringent size requirements for
@@ -233,6 +253,10 @@ reorganize this list later.  -gp
 
   - change all links to the stable documentation
 
+  - make a link from the old unstable to the next stable in
+    lilypond.org's /doc/ dir.  Keep all previous unstable->stable
+    doc symlinks.
+
   - doc auto redirects  to v2.LATEST-STABLE
 
   - add these two lines to http://www.lilypond.org/robots.txt:
@@ -242,6 +266,21 @@ Disallow: /doc/v2.PREVIOUS-STABLE/
 Disallow: /doc/v2.CURRENT-DEVELOPMENT/
 @end example
 
+- check for emergencies the docs:
+
+@example
+grep FIXME --exclude "misc/*" --exclude "*GNUmakefile" \
+  --exclude "snippets/*" ????*/*
+@end example
+
+- check for altered regtests, and document as necessary.  (update
+  tags as appropriate)
+
+@example
+git diff -u -r release/2.12.0-1 -r release/2.13.13-1 input/regression/
+@end example
+
+
 News:
 
         comp.music.research