@item
Switch to the release branch, get changes, prep release
-announcement:
+announcement. This requires a clean index and work tree. If the
+checkout displays modified files, you might want to run @code{git reset
+--hard} before continuing.
@example
-git checkout release/unstable
+git fetch
+git checkout origin/release/unstable
git merge origin
+make po-replace
vi Documentation/web/news-front.itexi Documentation/web/news.itexi
@end example
@item
-Commit, push, switch back to master:
+Commit, push, switch back to master (or wherever else):
@example
+git commit -m "PO: update template." po/lilypond.pot
git commit -m "Release: update news." Documentation/web/
-git push origin
+git push origin HEAD:release/unstable
+git checkout master
@end example
@item
If you do not have the previous release test-output tarball, download
it and put it in @code{regtests/}
+@item Prepare GUB environment by running:
+
+@example
+### my-gub.sh
+# special terminal, and default PATH environment.
+# import these special environment vars:
+# HOME, HTTP_PROXY, TERM
+env -i \
+ HOME=$HOME \
+ HTTP_PROXY=$HTTP_PROXY \
+ bash --rcfile my-bashrc
+@end example
+
+@example
+### my-bashrc
+export PS1="\[\e[1;33mGUB-ENV \w\]$ \[\e[0m\]"
+export PATH=$PATH
+export TERM=xterm
+@end example
+
+
@item Build release on GUB by running:
@example
make LILYPOND_BRANCH=stable/2.12 lilypond
@end example
-@item Check the regtest comparison in @file{uploads/@/webtest/} for
+@item Check the regtest comparison in @file{uploads/webtest/} for
any unintentional breakage. More info in
@ref{Precompiled regression tests}.
@item Switch back to master and get the updated news:
@example
-git checkout master
-git merge release/unstable
+git checkout origin/staging
+git merge origin/release/unstable
@end example
@item Update @file{VERSION} in lilypond git and upload changes:
@example
git commit -m "Release: bump version." VERSION
-git push origin
+git push origin HEAD:staging
@end example
BUILD_DIR=$HOME/src/build-lilypond
PICS=$BUILD_DIR/Documentation/pictures/out-www/
-EXAMPLES=$BUILD_DIR/Documentation/web/ly-examples/out-www/
+EXAMPLES=$BUILD_DIR/Documentation/ly-examples/out-www/
cd $BUILD_DIR
rsync -a $PICS graham@@lilypond.org:media/pictures
Run convert-ly on all files, bump parser minimum version.
@item
-Make FTP directories on lilypond.org
+Update lilypond.pot:
+
+@example
+make po-replace
+@end example
+
+@item
+Make directories on lilypond.org:
+
+@example
+~/web/download/sources/v2.14
+~/web/download/sources/v2.15
+@end example
+
+@item
+Shortly after the release, move all current contributors to
+previous contributors in:
+
+@example
+Documentation/included/authors.itexi
+@end example
+
+Also, delete old material in:
+
+@example
+Documentation/changes.tely
+@end example
+
+but don't forget to check it still compiles! also update the
+version numbers.
@item
Website:
@itemize
@item
-submit pots for translation: send url of tarball to
-translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
+submit po template for translation: send url of tarball to
+coordinator@@translationproject.org, mentioning lilypond-VERSION.pot
@item
update links to distros providing lilypond packages? link in:
-@file{Documentation@/web@/download.itexi}
+@file{Documentation/web/download.itexi}
This has nothing to do with the release, but it's a "periodic
maintenance" task that might make sense to include with releases.
@example
bin/gub mingw::lilypond-installer
make LILYPOND_BRANCH=stable/2.12 -f lilypond.make doc
-bin/gub --platform=darwin-x86 'git://git.sv.gnu.org/lilypond-doc.git?branch=stable/2.12'
+bin/gub --platform=darwin-x86 \
+ 'git://git.sv.gnu.org/lilypond-doc.git?branch=stable/2.12'
@end example
or