Hi Eric, Am Sun, 27 May 2007 11:06:48 +0200 schrieb eric b: >> But by any means I wanted to abdanon the OOo quality! So I'm O.K. >> if it takes another week to get the first "official" aqua build >> out. We only have to communicate it all the right way and we need >> to be honest in communication. > > > This is *exactly* what I asked : prepare everything quietly, and > prepare the servers, because the load will be high, you can > believe me. > > But one week only, not more. What is the problem at the end ?
I think the problem, if you want to call it so, is that currently we don't have a common sense on what to release as first alpha or to be more specific, which requirements and tasks are needed *before* releasing a first public alpha/devolpment snapshot/call it whatever you like to. So we need to make a to-do list. E.g.: 1. Give the build a self explanatory name - avoid that end-users take this as a final. 2. Write a short Readme 3. Make a list of known issues 4. Prepare a page/text file that tells the end-user where to report issues 5. If neccessary provide a short how-to on Issuezialla, especially that the issues need to be assigned to our "dummy" user and not to ericb. Please add what's missing. >> We're not allowed to make promises >> we cannot keep. > > > What do you mean with that ? E.g. tell the end-user this is the final look and feel or that he can use it as a productive version, that there is "support" for this version on the user-mailinglist etc. We need to make it clear this is a *real* alpha and by no means a stable version for your daily work and that we give no guarantee for data losses if he uses this version as his daily productive one. > aquavcl01 and aquafilpicker01 are *real*, and my changes are > commited (means in aquavcl01 now). Thanks. I believe you. > Just the process to integrate them su... , and will need 2 weeks > (at least), *starting from the day* we will start the integration > (please retain we started to discuss the 25th May, and nothing > has been done yet ...) . So basicly we need to teams. Team 1. Prepare the Readmes, How-Tos, websites etc so that the devs in team 2 can focus on their stuff Team 2: Start integrating cws aquanativefilepicker01 into master workspace and resync aquavcl01 with most current milestone. Once this is done we can start with a basic *intern* QA of this build - you'll never know if the current milestone is a good or bad one for aquavcl01 before you resync aquavcl01 and did a first build - and if no regressions compared to the state we currently have are found, release aqua OOo Alpha to the public. > To be honest, I'm *not optimistic* at all, *one week only* will > be sufficient, and this delay won't help for our credibility. > > That's the main reason why I proposed my builds : we control the delay. If this is o.k. with the others I would second this but we need to make sure that this is a one time exception and won't make the rule. Kind regards, Eric Hoch -- ## de.OpenOffice.org - Office für MacOS X, Linux, Solaris & Windows ## Openoffice.org - ich steck mit drin! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
