On Thu, Feb 27, 2014 at 3:31 PM, <i...@raphaelbircher.ch> wrote: > Hi at all > > Zitat von jan i <j...@apache.org>: > > >> On 27 February 2014 16:58, Vladislav Stevanovic < >> stevanovicvladis...@gmail.com> wrote: >> >>> Is it too late for update Serbian language? >>> Wlada >>> >>> >>> 2014-02-27 16:50 GMT+01:00 Jürgen Schmidt <jogischm...@gmail.com>: >>> >>> > Hi, >>> > >>> > we are still verifying some fixes to identify the Beta as real beta, >>> > means some branding elements, names etc. And we are working on some >>> > serious bugfixes that we have identified already. >>> > >>> > The current plan is to start the build tomorrow and do the upload over >>> > the weekend. That means we should have a RC for AOO 4.1 beta available >>> > at the beginning of next. >>> > >>> > The new icons are still not complete and I am not sure how we can or >>> > should continue here. Replacing them for the final release is probably >>> > not a good idea. >>> > >>> > Work remaining before beta >>> > >>> > 1) Defect verification >>> > >>> > 2) Release Notes >>> > check, update and finalize the release notes [1] >>> > >>> > 3) Communications >>> > Clarify the communication/promotion for the beta. For example how many >>> > users do we want to reach with the beta. >>> > >>> > 4) Release vote >>> > >>> > Based on this a possible schedule can be >>> > >>> > March 4th: availability of AOO 41. Beta RC + start vote >>> >> >> just for my understanding, dont we need to vote on the beta as well as the >> release. We send the beta out to general public, that would normally >> require a vote (might be a fast one). > > > I wouldn't make a beta as a RC. After a Beta you have normaly several > showstopers to fix. I recall, RC = Release Candidate wich means, that we > assume the build is ready for release. Beta... wait two or tree weeks fix > showstoppers, and then a RC. And the important tests are not the one in the > RC, the important tests are at the build befor RC. Else we make the same > mess as in the 4.0.0. >
It is an Release Candidate because a beta is a Release. When we vote on the RC we agree it is ready for release as a beta. After that we'll fix more bugs and have another RC and vote for that to be released as 4.1. I think the confusion is that we use the word "release" into two ways: 1) The Apache definition of a release == something that a PMC votes on and approves for publication and public consumption 2) Release as the final version of a product cycle One way to avoid confusion is to use "GA" for the 2nd meaning (GA= General Availability). If we do that then it is clear: 1) We have a RC for the Beta and then we release the beta 2) Some weeks later, after fixing more bugs we have an RC for the GA and then we release the GA Regards, -Rob > Greetings Raphael > > >> >> rgds >> jan I. >> >> >>> > March 10th: public availability of AOO 41. Beta (until March 31th) >>> > ...: additional snapshot builds based on the beta including showstopper >>> > fixes >>> > April 2th: availability of AOO 4.1 RC >>> > April 7th: public availability of AOO 4.1 >>> > >>> > Any opinions or feedback >>> > Juergen >>> > >>> > >>> > [1] >>> > >>> >>> https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Notes >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>> > For additional commands, e-mail: dev-h...@openoffice.apache.org >>> > >>> > >>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
