use automatic bzr translations

[Luca Invernizzi]

* Also, you should definitely consider using:

  * Automatic bzr translation exports [3] [4]

Which are in my opinion two of the coolest features the Launchpad
Translations team has developed in recent times. It will ease your life as a maintainer by committing translations automatically and not having to manually exporting them. Basically, this will allow the whole translations handling process to be automated (apart from updating the POT file and sending a call for translations before release).

[1] http://www.glatzor.de/projects/python-distutils-extra/
[2] https://launchpad.net/ubuntu/+source/python-distutils-extra
[3] http://blog.launchpad.net/general/exporting-translations-to-a-bazaar-branch
[4] http://blog.launchpad.net/translations/screencast-exporting-translations-to-a-bazaar-branch

see https://code.edge.launchpad.net/~dpm/gtg/i18n-improvements/+merge/21218

[Luca Invernizzi (invernizzi)]

Now these two branches recieve the daily export of the translations from launchpad:
lp:~invernizzi/gtg/trunk-translations
lp:~invernizzi/gtg/0.2-translations

[I had to make them mine because only personal branches are currently supported]

Updating the translations it's just a matter of merging those branches.

[David Planella (dpm)]

Awesome, thanks for looking into this, Luca

> [I had to make them mine because only personal branches are currently supported]

That's only a temporary workaround for the bug in Launchpad Translations. Once you've chosen the branches for translation export (as you've already done), you can change the branch owner back to the team.

[Luca Invernizzi (invernizzi)]

Done that. Now branches are:

lp:~gtg-user/gtg/trunk-translations
lp:~gtg-user/gtg/0.2-translations

"ReleaseProcess" on the Gtg wiki has been updated (http://live.gnome.org/gtg/ReleaseProcess).