I don't agree, SirVir. even now it shouln't be "Fix committed" because the translations need to be merged from branch to the trunk.
1. New code is written which contains translatable strings. A bug should be only filed, when the string is not marked translatable => Bug confirmed
2. Some dev creates new translation catalogs => Bug triaged / In Progress
3. Someone translates it on launchpad => In Progess
4. Some dev merges translation branch to trunk => Fix committed
5. A new widelands binary package is released => Fix released
But this is really a bit overhead for only in launchpad missing translatable strings.
Is there a way to automating the updating pots/merging branch to trunk steps at least once a week?
Then the work of ppl translating on launchpad would be visible much earlier in the dev builds...
I don't agree, SirVir. even now it shouln't be "Fix committed" because the translations need to be merged from branch to the trunk.
1. New code is written which contains translatable strings. A bug should be only filed, when the string is not marked translatable => Bug confirmed
2. Some dev creates new translation catalogs => Bug triaged / In Progress
3. Someone translates it on launchpad => In Progess
4. Some dev merges translation branch to trunk => Fix committed
5. A new widelands binary package is released => Fix released
But this is really a bit overhead for only in launchpad missing translatable strings.
Is there a way to automating the updating pots/merging branch to trunk steps at least once a week?
Then the work of ppl translating on launchpad would be visible much earlier in the dev builds...