+@item @strong{Release prep}:
+Only translation updates and important bugfixes are allowed.
+
+@end enumerate
+
+
+@node Minor release checklist
+@section Minor release checklist
+
+A @qq{minor release} means an update of @code{y} in @code{2.x.y}.
+
+@subheading Pre-release
+
+@enumerate
+
+@item
+Switch to the release branch, get changes, prep release
+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
+
+@item
+If you do not have the previous release test-output tarball, download
+it and put it in @code{regtests/}
+
+@item Build release on GUB by running:
+
+@example
+make LILYPOND_BRANCH=release/unstable lilypond
+@end example
+
+@noindent
+or something like:
+
+@example
+make LILYPOND_BRANCH=stable/2.12 lilypond
+@end example
+
+@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.
+
+@warning{Always do this for a stable release.}