Revert "CG: add updating of lilypond.pot in the release process"

This reverts commit f7d264fa89c39f8d86e9ba5eb991ee904ce3d0be.

Those instructions relied on in-tree builds, whereas we use
out-of-tree builds.

diff --git a/Documentation/contributor/release-work.itexi b/Documentation/contributor/release-work.itexi
index 4828d1ae0ea348b461df37346347411e7177fb93..baa68a85e468768c8defbf0d24412aaba1570134 100644 (file)
--- a/Documentation/contributor/release-work.itexi
+++ b/Documentation/contributor/release-work.itexi
@@ -83,7 +83,6 @@ checkout displays modified files, you might want to run @code{git reset
 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
 
@@ -91,7 +90,6 @@ vi Documentation/web/news-front.itexi Documentation/web/news.itexi
 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
@@ -299,13 +297,6 @@ various websites, so be brief.
 @item
 Run convert-ly on all files, bump parser minimum version.
 
-@item
-Update lilypond.pot:
-
-@example
-make po-replace
-@end example
-
 @item
 Make directories on lilypond.org:
 
@@ -369,8 +360,8 @@ Disallow: /doc/v2.CURRENT-DEVELOPMENT/
 
 @itemize
 @item
-submit po template for translation: send url of tarball to
-coordinator@@translationproject.org, mentioning lilypond-VERSION.pot
+submit pots for translation: send url of tarball to
+translation@@iro.umontreal.ca, mentioning lilypond-VERSION.pot
 
 @item
 update links to distros providing lilypond packages?  link in: