Hi translators (and Steve)
This is a proposal for how we do translations. The general principle is that
all translations are coordinated through Launchpad.
A briefer version can be found at
http://bitbucket.org/tortoisehg/stable/wiki/edit/developers/Translation
We have our build master: Steve
He is responsible for
- downloading .po files from launchpad, merging them into bitbucket (using
internal:other if it gives him any trouble) - during major and minor
releases
We have a team of translation drivers: Peer (me) and Yuki.
They are responsible for
- generating .pot files, uploading them to launchpad
We have a number of very active translators: Yuki, Paolo
They are responsible for
- downloading individual .po files from launchpad, merging them into
bitbucket - when working with unstable
We have a number of ordinary translators
They are responsible for
- translating strings on launchpad
I'm trying to establish two translation series on launchpad: stable and
unstable (=default branch)
- Stable is where most translators should work.
- Unstable is for translators that want to be on the bleeding edge.
=== Stable translations ===
I suggest we pull .po files from launchpad at every release and store them
in the stable branch.
For major releases we have feature freeze at -2 weeks, which triggers a
merge from default to stable. Right after this the I18N team should generate
a fresh .pot from stable and upload it to launchpad.
At -1 week we have string freeze (still on stable) which should again
trigger a fresh .pot upload to launchpad stable series.
Just before release, we download all .po files from launchpad stable and
commit them to bitbucket stable. I think Steve did this last time. If we
want real tight deadlines (and fewer build dependencies), that is the best
way.
Every minor release, we (Steve) pull .po files from launchpad stable, commit
them to bitbucket stable and merge to bitbucket default branch.
=== Unstable translations ===
There is no fixed schedule for generating .pot and uploading them to
launchpad unstable series. Neither is there a schedule for pulling .po files
and including them into nightly builds. This is to reduce burden on
translators and on our build master.
Very active translators, like Yuki, might want to work on the unstable
branch - so the developer wiki should probably have a text that describes
how to do the translation cycle.
I guess this would be
1. generate pot file from default branch
2. upload pot to launchpad unstable series
3. download the relevant po from launchpad unstable series (to get the work
others have done)
4. upload changed po to launchpad unstable series
5. test translation
6. commit po to default branch (so the translations will be in the next
nightly build)
Normal translators would not have to do steps 1-2
It would be possible to work without launchpad, skipping steps 2-4.
The merges between default branch and stable will ensure that translation
strings only have to be done on one branch.
=== Working without Launchpad ===
I plan to write some scripts that transfer changed .po files to launchpad,
so it would be possible to work entirely on the bitbucket repo. In case of a
merge conflict I will let the launchpad version win. The translator would
then have to manually re-merge the bitbucket repo - which would then be
pushed to launchpad.
This is not ready yet.
Regards,
Peer
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Tortoisehg-develop mailing list
Tortoisehg-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
