I have been thinking a bit about how the i18n workflow interacts with our standard merging procedure from 0.12-stable to trunk. Considering the following:
- We will be making regular releases from 0.12-stable, whereas trunk will stay unreleased for some time. - The messages on trunk evolve much more quickly than on 0.12-stable, and may be added and removed many times over. - Merging message catalogs and translations probably becomes very tedious very quickly. I would suggest that we only ever extract the message catalog on 0.12-stable, and that translators work exclusively on that branch. The message catalog and translations on trunk should only ever be updated by (trivial) merges from 0.12-stable. This means that trunk will be largely untranslated for quite some time. When 0.13b becomes close to being released, we can update the catalog on trunk and update the translations on trunk. From that point, all merges to the catalog and translations from 0.12-stable should be blocked. Therefore, translation work will start being duplicated, but at the same time, work on 0.12-stable should have slowed down considerably, so this shouldn't have too much impact on translators. If everyone agrees, I would kindly ask our translators to switch their working copies to 0.12-stable, and work from there. I will merge the few translation changes that have already happened on trunk back to 0.12-stable. My apologies if I have just stated the obvious, but I haven't seen this documented anywhere, so I wanted to make sure we were all on the same page. -- Remy
signature.asc
Description: OpenPGP digital signature
