On 10/18/05, Andre Schnabel <[EMAIL PROTECTED]> wrote: > 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) >
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. 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. :-) > > 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). > 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? > > 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. > One of them is iz47190 ( http://ko.openoffice.org/issues/show_bug.cgi?id=47190 ). In Korea, we typically use square brackets to designate button names. However, those are special characters in MSI database and eats up button names in Windows setup. I found the way to escape them in MSDN and the problem was fixed in milestone build. I feel it is my fault not to check rc builds carefully. 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. > 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. > I personally build Windows version for my own purpose, but no official community build yet. I am considering to provide community build with Sun's build together. I believe it will make easy to handle some Korean specific issues. For example, iz55356 ( http://www.openoffice.org/issues/show_bug.cgi?id=55356 ) is one of demanding issues but failed to get developer's attention. Many votes, easy to fix but Korean-specific. :-) Thanks for your kind answer again. Jeongkyu -- Jeongkyu Kim OpenOffice.org Korean community lead Official website http://ko.openoffice.org Community forum http://oooko.net/ Personal blog http://oooko.net/gomme --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
