Merge lp:~jr/bzr/i18n-release-process-doc into lp:bzr

Proposed by Jonathan Riddell
Status: Merged
Approved by: Vincent Ladeuil
Approved revision: no longer in the source branch.
Merged at revision: 6135
Proposed branch: lp:~jr/bzr/i18n-release-process-doc
Merge into: lp:bzr
Diff against target: 68 lines (+39/-0)
1 file modified
doc/developers/releasing.txt (+39/-0)
To merge this branch: bzr merge lp:~jr/bzr/i18n-release-process-doc
Reviewer Review Type Date Requested Status
Vincent Ladeuil Approve
Review via email: mp+75161@code.launchpad.net

Commit message

add translations to release process

Description of the change

add translations to release process

To post a comment you must log in.
Revision history for this message
Vincent Ladeuil (vila) wrote :

Except for the tweaks mentioned on IRC, go ! Land !

I'll test that soon enough and let you know how it worked ;)

review: Approve
Revision history for this message
Jonathan Riddell (jr) wrote :

sent to pqm by email

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/developers/releasing.txt'
2--- doc/developers/releasing.txt 2011-09-06 09:11:54 +0000
3+++ doc/developers/releasing.txt 2011-09-13 12:40:26 +0000
4@@ -246,6 +246,18 @@
5 this slow you down too much. This script accepts options you may find
6 useful, use ``./tools/check-newsbugs.py`` to display its usage.
7
8+#. For beta releases update the translation template::
9+
10+ make -f po/bzr.pot
11+
12+ This is especially important for the final beta release which is
13+ when translations are frozen and translators are requested to make
14+ the translations.
15+
16+#. For stable releases update the translations::
17+
18+ bzr merge lp:~bzr-core/bzr/bzr-translations-export-x.y
19+
20 #. Commit these changes to the release branch, using a command like::
21
22 bzr commit -m "Release 2.3.1"
23@@ -406,6 +418,9 @@
24 You may also need to do `At the start of a series cycle`_ if you're starting
25 a new series.
26
27+The final beta - branching and translations
28+-------------------------------------------
29+
30 A word of caution: the instructions above works well for all releases but
31 there is one special case that requires a bit more care: when you release
32 the *last* beta for a given ``x.y`` series (from trunk aka lp:bzr), you need
33@@ -436,6 +451,26 @@
34
35 #. Open ``lp:bzr/x.y`` for bug fixes
36
37+You also need to ensure Launchpad is set up to import/export
38+translations for the new branch and inform translators.
39+
40+#. Push a branch::
41+
42+ bzr push lp:~bzr-core/bzr/bzr-translations-export-x.y
43+
44+#. On the translations series synchronization settings page
45+ <https://translations.launchpad.net/bzr/x.y/+translations-settings>
46+ turn on ``Import template files`` then for exports click ``Choose a
47+ target branch`` and point it at the branch you just pushed.
48+
49+#. E-mail translators to announce that the forthcoming stable release
50+ of bzr is ready for translations. Send to
51+ ``translators@lists.launchpad.net`` and
52+ ``ubuntu-translators@lists.ubuntu.com``.
53+
54+#. The series is now frozen for strings and API, see below for adding
55+ that to the announcement.
56+
57 Announcing the source freeze
58 ----------------------------
59
60@@ -452,6 +487,10 @@
61 the freeze. For older series supported only via SRUs for Ubuntu, we don't
62 control the process as tightly so guessing the date is not appropriate.
63
64+ For the final beta release include in your announcement a notice of
65+ API and translation freezes nothing that public methods should not
66+ be removed or changed and strings should not be added or changed.
67+
68 #. Pause for a few days.
69
70