git fetch
git checkout origin/release/unstable
git merge origin
+make -C $LILYPOND_BUILD_DIR po-replace
+mv $LILYPOND_BUILD_DIR/po/lilypond.pot po/
vi Documentation/web/news-front.itexi Documentation/web/news.itexi
@end example
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 HEAD:release/unstable
git checkout master
@enumerate
-@item Switch back to master and get the updated news:
+@item Update the current staging branch with the current news:
@example
+git fetch
git checkout origin/staging
git merge origin/release/unstable
@end example
git push origin HEAD:staging
@end example
+If the push fails with a message like
+
+@example
+ ! [rejected] HEAD -> staging (non-fast-forward)
+@end example
+
+@noindent
+it means that somebody else updated the staging branch while you were
+preparing your change. In that case, you need to restart the Post
+Release process. Otherwise, proceed:
@item (for now) do a @code{make doc} and manually upload:
@item
Run convert-ly on all files, bump parser minimum version.
+@item
+Update lilypond.pot:
+
+@example
+make -C $LILYPOND_BUILD_DIR po-replace
+mv $LILYPOND_BUILD_DIR/po/lilypond.pot po/
+@end example
+
@item
Make directories on lilypond.org:
@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: