Hi Clytie,
as Andre wrote some mails ago, here are the release process and the
testing of a localized build are mixed up.
As I could read out of your mails you want to make testing (translation
and localization testing) on a new language. And in the same way you
want to release that version. This isn't possible in a timeframe for
a release testing cycle. The testing of a new language takes much more
time.
And what should be the result of such a release? If the translated
version is build first the qa team (perhaps only one person) will find
many bugs in translation, localization and other things. So could it be
released with 10, 20 or 100 of such errors? Nobody can answer these
questions. So first testing (will take some weeks/months) has to be done
and after that the the major issues have to be fixed. And then the
language builds can be release in perhaps the next version without major
issues problem. On the other hand, the TestTool scripts have to be
adapted for each new language. If this isn't done, the tests will throw
many localization bugs.
So why not make testing on OOo2.1 builds, report and/or fix all major
translation issues until end of January and make a small release testing
(check fixed issues and make a sanity check) of OOo2.2? The release
schedule is End of February.
As a new member of QA on OOo, your feedback on broken or difficult
processes and bad information on the web sites or anything else is still
needed, useful and welcome. So do not stop posting it.
Regards,
Thorsten
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
