* Minor release checklist::
* Major release checklist::
* Release extra notes::
-* Administrative policies::
@end menu
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.
+@item Check the regtest comparison in @file{uploads/@/webtest/} for
+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
@enumerate
@item If you're not right user on the webserver, remove the "t"
-from the rsync command in @file{test-lily/rsync-lily-doc.py} and
-@file{test-lily/rsync-test.py}
+from the rsync command in @file{test@/-lily/@/rsync@/-lily@/-doc@/.py} and
+@file{test@/-lily/@/rsync@/-test@/.py}
@code{graham} owns v2.13; @code{han-wen} owns v2.12.
@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
Before release:
-* write release notes. note: stringent size requirements for
+* write release notes. note: stringent size requirements for
various websites, so be brief.
* write preface section for manual.
-* submit pots for translation : send url of tarball to
+* submit pots for translation: send url of tarball to
translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
* Check reg test
@end enumerate
-@node Administrative policies
-@section Administrative policies
-
-Not really release-specific notes, but I don't see enough material
-here to make it a separate chapter, and the release person will
-probably be the one taking care of this anyway.
-
-@subsubheading Language-specific mailing lists
-
-A translator can ask for an official lilypond-xy mailing list once
-they've finished all @qq{priority 1} translation items.
-
-@subsubheading Performing yearly copyright update (@qq{grand-replace})
-
-At the start of each year, copyright notices for all source files
-should be refreshed by running the following command from the top of
-the source tree:
-
-@example
-make grand-replace
-@end example
-
-Internally, this invokes the script @file{scripts/build/grand-replace.py},
-which performs a regular expression substitution for old-year -> new-year
-wherever it finds a valid copyright notice.
-Note that snapshots of third party files such as @file{texinfo.tex} should
-not be included in the automatic update; @file{grand-replace.py} ignores these
-files if they are listed in the variable @code{copied_files}.