On Fri, 27 Mar 2009, Mark Mitchell wrote: > 8. Regenerating .pot files.
I have done this, and applied this patch to reflect that submitting a snapshot to the TP is not necessary after creating a release branch if one was submitted during stage 3 or 4 (now we have a long stabilisation period on trunk and a comparatively short one on the branch before release, submitting one from trunk is the right approach). Index: branching.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.25 diff -u -r1.25 branching.html --- branching.html 23 Oct 2006 19:49:49 -0000 1.25 +++ branching.html 28 Mar 2009 07:31:16 -0000 @@ -54,7 +54,8 @@ <li><a href="translation.html#regen">Regenerate <code>gcc.pot</code></a> and <code>cpplib.pot</code>. <a href="http://gcc.gnu.org/translation.html#submit";>Send them -to the translation project</a>.</li> +to the translation project</a> if no snapshot of this version was sent +during development stage 3 or 4.</li> <li>Create new versions in Bugzilla corresponding to the new mainline version. This can be accomplished by choosing products, choosing gcc, Index: translation.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/translation.html,v retrieving revision 1.10 diff -u -r1.10 translation.html --- translation.html 3 Aug 2007 10:33:41 -0000 1.10 +++ translation.html 28 Mar 2009 07:31:16 -0000 @@ -39,7 +39,7 @@ <ol> <li>Just before each release (so the file is current in releases).</li> -<li>Just after a new release branch is made (so that a snapshot can be +<li>At some time during development stage 3 or 4 (so that a snapshot can be submitted to the Translation Project and translators have a chance to catch up before the release).</li> </ol> -- Joseph S. Myers jos...@codesourcery.com
