* Betr.: " [tryton-dev] About some issues faced during the last release process" (Mon, 7 May 2012 21:08:45 +0200):
> I would like to report some issues I faced during the last release:
>
> - format of the po file
> Some have pushed files not generated by the tryton export which means
> it was not wrapped correctly.
> This is wrong, we must generate files always the same way to minimize
> the changeset diff. This is important when you search in the history.
> (exception of the client which uses Babel).
Of course, I am prefering minimzed changesets as well.
OTOH I see, that some contributors are assigning copyright to their
translations - something not provided so far by trytond itself. What's your
idea of a common export interface?
> - multiple commit on the same file
> During the translation window, translators must commit only once the
> translation of a module. We don't need to have WIP in the repository.
> The repository is not a tool to send WIP files. Again we must have a
> clean history and try to reduce the number of changeset on a file.
I don't agree. All the code is work in progress. I for my share try to push
translations as early as I am able to do, thus enabling possible testers to
also check the translation. And of course I am trying to minimize fixes after
the first push (in fact for 2.4 I only had to update one translation due to a
fix pushed by upstream during string freeze), but a fix is a fix ;), and it is
the privilege of translators to push their fixes during string feeze.
Conclusion: Try to give translators, especially newcomers, a hand and a
workplace, where they can learn to do their work in an efficient way. New
languages in particular need multiple iterations, if they shall be well done.
As time goes by everyone will learn to it right.
> - commit during the release
> When the date of the release is reached, no commit should be made
> (except the one of the release manager). Otherwise it is too complex
> work for the release manager. And again the history is not clear.
> For now, nothing prevent it, we just trust everyone to respect it.
+1
> - translation outside the release window
> This is just WIP commits because the strings are not freezed so it is
> not needed to run after them.
> If some translators find they don't have enough time (3-4 weeks)
> during the release window, they can start (or maintain) outside the
> main repository an up to date translation as far as it doesn't trouble
> the history of the main repository.
> Also we can try to setup a transifex instance on tryton.org if it is
> needed (need to be patched to remove GNU headers).
Translation is development, the same way as code is. There has to be an *easy*
way to test translations. So far the only way is to push to the repos.
> - improvement during the translation process
> Some translators try to improve some strings in their translation
> process. This is bad because it just improves the software for their
> language and not for everyone, it is the english that should first be
> improved. So this should be done during the development process.
It is a contradiction: Fixing strings during string freeze.
I am in favor of a general string review by some native speaker since years...,
and yes, it should be done at the *beginning* of a release cycle.
--
Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg
Tel: +49(761)471023
Fax: +49(761)4770816
http://m9s.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6
signature.asc
Description: PGP signature
