Andre Schnabel wrote:
Hi David,
We have got updated translations for our languages, but they will
only be included in 2.0.1 because we weren't in time.
However, this means that I would rather get our testers to QA our
updated language builds than the 2.0.0 versions which have incomplete
translations.
How should this fit into the QA process?
well .. so your localizetion would stay at red (untested) or yellow
(in qa). That would mean, the binaries are available but have not
(yet) final quality).
There are some options, to get your localization to green:
- wait for 2.0.1 with updated translation (I'd prefere this one, as
2.0.1 is scheduled for end of November)
ok, we plan to submit the translation for 2.0.1 anyway, so this one is
definitely going to happen.
- build your own 2.0.0 with translation included, test it and release
it (possible, but might cause more errors, as your builds would come
from another build environment)
We are building our own now on Windows and Linux, so we are looking at
the QA process now. This should at least make the road to 2.0.1 quicker
from the official build point of view. I've also found that we can
install our language packs on top of the official English build which is
really nice.
Incidentally, it would be nice to have a web page that tracks the QA
tests so different people can share the load. Has anyone got something
like this?
- ignore missing translation and release anyway (should only be done,
if the missing parts are really not so important - absolutely not the
preferred way, but nobody would release a 100% perfect localization)
Well our localizations have now definitely reached a "good enough"
status that most people could use them with out a problem. So for people
who want to, they will be able to download them. But I think it makes
sense to wait for official 2.0.1 builds before including it on the ooo
downloads site
Thanks for the reply.
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
