Hi,
Thanks for your kind answer. Currently, _Korean team relies on Sun's
build_ and provide it through Korean NL website. And, my question was
about smoke testing which allows to change rc3 build into stable one.
As far as I know, if community submits a report that rc3 is
satisfactory to formal release then QA can change rc3 into stable,
correct? I meant the due date for the smoke testing report.
Hmm.. the due date for stoppers, that affect the global builds is about
two days before global release. The due date for a GO is about two days
before local release.
You don't need to present the full results. We are used to trust in the
local QA represantatives. If they give a GO, we accept this in most
cases. So .. best (and fastes way) is, if your QA team updates the
status page and files an issue to distribute your builds to the mirrors
(if you are giving a GO).
Actually, until 1.1.X release, we haven't got a chance to do smoke
testing and have provided rc3 as formal release. And this confuses
many users. With increasing interest in OO.o 2.0, I decided to correct
situation. :-)
:-)
...
Let me clarify my understanding. If we find a Korean specific stopper
in rc3 during smoke testing, then we have to wait Sun's next build
cycle or we may provide community build. Is that correct?
Yes. But you should ask at [EMAIL PROTECTED] or at the IRC channel, if
Release Engineering could speed things up or provide a build with fixes.
For now, I will focus on solving the issues with l10n team. Once they
are fixed then I will go to release list and check when next build is
available.
Ah great. Just what I said ;-) (Hope it can be fixed soon)
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
