Hi,
tora - Takamichi Akiyama schrieb:
Look at the status pages of localized builds and think of current
situation.
http://qa.openoffice.org/localized/status.html
http://www.qatrack.org/ooo/view.php
There is *no* OOo available for a bunch of languages.
Depends on what you call available. There is no official stable release
for many languages.
- Firstly, English one will be released.
- Secondly, QAed ones will be released with certification of QAed.
- Finally, the rest will be released without certification after the
deadline.
I strongly disagree to the last point.
Althgouh I do the same as Sophie (approve a platform where I don't have
access) I do only approve builds where I *know* someone has tested the
builds (at least installed it and edidet some documents successfully).
This is the reason why I always said that the test scenarios are a
guideline, bit it is up to the qa representative to decide about the
approval.
But the current situation for many languages is different: we do not
know if anybody has ever tried to use this language. We have absolutely
*no* feedback. See Rene's comments at the IRC log to see what might
happen - we might release a localization as offically stable, even
thoguh errors are visible at the first sight.
For the reason that most functionalities of OOo can be considered
language independent, we could give a GO to not-yet-completely-tested
builds. How about defining a quite simple sanity QA test that covers
only installation and releasing the target build if the installation
is successful?
No Problem: TCM has priorities, we can define own scenarios in TCM ..
and I often asked for input on the Release sanity scenario ... well I
never got real input so I thought it was perfect.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
