Developer Area/Language Packs/Launchpad Branching: Difference between revisions
From Mahara Wiki
< Developer Area | Language Packs
(Created page with "= Create a new code branch = Create a new code branch in the mahara-lang launchpad project for importing pot templates. This should contain a copy of the latest mahara/mahara.p…") |
|||
| Line 23: | Line 23: | ||
= Set up translation import and export for the new series = | = Set up translation import and export for the new series = | ||
In the translation synchronisation settings for the 1.5 series, set the translation to "Import template files" from the official branch (on the trunk series, we "Import template and translation files", but it can potentially overwrite translations, so we don't do that for a stable branch). | In the translation synchronisation settings for the 1.5 series (https://translations.launchpad.net/mahara-lang/1.5/+translations-settings), set the translation to "Import template files" from the official branch (on the trunk series, we "Import template and translation files", but it can potentially overwrite translations, so we don't do that for a stable branch). | ||
In the export synchronisation settings, export translations for the series to a new branch called lp:~mahara-lang/mahara-lang/1.5_STABLE-export. This should be automatically created in a day or so, once there are translations to export. This is the branch where the langpacks.mahara.org tarballs | In the export synchronisation settings, export translations for the series to a new branch called lp:~mahara-lang/mahara-lang/1.5_STABLE-export. This should be automatically created in a day or so, once there are translations to export. This is the branch where the langpacks.mahara.org tarballs | ||
Revision as of 13:10, 17 April 2012
Create a new code branch
Create a new code branch in the mahara-lang launchpad project for importing pot templates. This should contain a copy of the latest mahara/mahara.pot from master. Roughly, do something like this, from an existing up-to-date local copy of the mahara-lang bzr repo:
mkdir 1.5_STABLE cd 1.5_STABLE bzr init mkdir mahara cp ../master/mahara/mahara.pot mahara/ bzr add mahara/mahara.pot bzr commit bzr push lp:~mahara-lang/mahara-lang/1.5_STABLE
Check that the branch has appeared (with the mahara.pot file) under https://code.launchpad.net/mahara-lang
Create a new series
Create the new series under the mahara-lang project on launchpad at https://launchpad.net/mahara-lang/+addseries
You should set the official series branch to the one you just created (~mahara-lang/mahara-lang/1.5_STABLE). Once that's done, launchpad calls the branch by the abbreviated name lp:mahara-lang/1.5
Set up translation import and export for the new series
In the translation synchronisation settings for the 1.5 series (https://translations.launchpad.net/mahara-lang/1.5/+translations-settings), set the translation to "Import template files" from the official branch (on the trunk series, we "Import template and translation files", but it can potentially overwrite translations, so we don't do that for a stable branch).
In the export synchronisation settings, export translations for the series to a new branch called lp:~mahara-lang/mahara-lang/1.5_STABLE-export. This should be automatically created in a day or so, once there are translations to export. This is the branch where the langpacks.mahara.org tarballs come from.
Update the scripts
Update the langpack scripts. In the mahara-scripts repo, there are two files that need to be updated with the new branch name:
mahara-langpacks/langpacks.pl (which generates langpack tarballs from lp:~mahara-lang/mahara-lang/1.5_STABLE-export)
mahara-langpacks/update-pot.pl (which pushes new changes to English strings to lp:mahara-lang/1.5 to be translated)
Once the scripts are committed, deploy the scripts by generating a new custom-site-mahara-langpacks debian package. Run
fakeroot debian/rules binary
within your mahara-scripts checkout. The resulting .deb can be installed over the existing one (currently on chatter.catalyst.net.nz).