Hi,
1. Is there any due date on the testing?
We have a date for the (global) final release, what means source /
english binary release and some localizations. (for 2.0 this is set to
Oct. 10th 05).
If you want to join the global release, you should give a GO about 2
days before this date. If you have bugs, that would stop the global
release - it's the same (but should be reported as soon as possible)
2. If we find a problem regarded as show stopper, how much time we
have for fixing it?
Depends, if it is a stopper for global release or for Korean "only". If
only a localized version is deleayed, it's up to the native lang project
to define the release date and readyness. This may sound dissatisfying
to the native lang teams, but it has been the practice for years now.
(We are an open source project ... and are often critcized not to follow
the release early - release often rule).
For example, 2.0 rc3 Korean build has incomplete messages and missing
buttons names in Windows setup. And there was a opinion through
community forum that the problem needs to be fixed in 2.0 release
because it makes OOo look very naive to first time users.
In fact, the problem had been fixed already but appeared again
possibly by new translation from Sun. Now I wonder if it is possible
for Sun to provide new Korean build soon after fixing the issue.
Is there an issue for this? If not, file an issue immediately and ask at
releases list, if developer / release engineering could pay attention to it.
Do you have other builds available, that are not done by the Sun team?
Would be helpfull, to guess if this is a problem in the build
environment or in the sources.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
