Hi Sophie,
sophie schrieb:
Hi all,
Further thinking near to the end of this round for 3.1, I would like to
discuss possibilities of changes in the localization process. I'm not
aware of the technical part with cws, so I may tell stupidities, and
forgive me for that, but at least, I want to try :)
If I question EIS, I found 7 cws containing UI and Help changes for 3.2,
only one is yet nominated, none integrated.
Won't it be possible to get an extraction of the strings every 3 of 4
snapshots and get them merged in Pootle then makes cws of them.
You mean extraction of strings from "nominated" CWSs? That would be
possible. But you would normally only gain a few days that the CWS needs
to switch from "nominated" to "integrated". Currently we have a special
situation with a larger backlog of CWS, so that the time between these
two states is a bit higher.
Make those cws build by buildbots and merge those small cws in a final
one called localizationxx?
Ivo is working on a semi-automated process to build l10n CWSs, so that
such CWSs might be created more often than at the time. Btw., for this
goal it is not necessary to put data into Pootle from CWSs that are not
yet nominated.
Discussing with Andre he told me about that rsync of the cws may cause
issues and integration of Pootle changes in the cws may be problematic
also.
The goal I think we all like to get at would be to have more time for
translation and get aware of irrelevant parts or errors earlier, more
time to test smaller translations, and may be proceed in smaller
integration steps where we can check for translation from language packs
delivered by buildbots.
Agreed. This is exactly why Ivo, for quite some time now, is working on
the aforementioned process improvements.
I don't know if fragmenting this in cws is a way to think and is better
than only a large one at the end, again I have not enough technical
skills for that.
Kind regards
Sophie
Kind Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
