Hi *, On Fri, Jul 15, 2005 at 10:48:41AM +0800, Jacqueline McNally wrote: > Andre Schnabel wrote: > >Hi Jacueline, all, > >>Von: Jacqueline McNally <[EMAIL PROTECTED]> > >[...] > >I think we need to be a little more precise with our wording. > >I just take wikipedia as reference, as it tells, what most people think, > >what a RC is: > >http://en.wikipedia.org/wiki/Release_candidate#Release_candidate > >"The term release candidate can refer to a final product, ready to release > >unless fatal bugs emerge. > >... for versions that are substantially complete, but still under test, ... > >for final testing of versions that are believed to be bug-free, and may go > >into production at any time." > > This definition works well if there is a finite group working on the > release cycle. But here, and with other OSS, everyone has the > opportunity to be involved in the progression of the software through > its release cycle.
That's nonsense. This definition works well with software and communities of every size. Before the RC, there are snapshots, alphas, betas. This definition is also what has been the guideline within OOo all the time. That the assumtion "ready for production use" turned out not to be true in some cases is a totally different thing. And your statement "everyboy can be involved" has nothing to do with the definitionn of a RC and has nothing to do with what we release as RC. > >So, at this time, we *know* that our RC is not ready to be released. A > >showstopper has been raised yesterday at the releases list. It has already > >been marked as fixed, so I'd expect to see a new RC within the next few > >days. > > Yes, we will, so we will have another one. But don't you think it is > better that many more people are able and willing to download and test > the "releases that are not yet production" ? No. Not when it is a release candidate and the main way of installation is broken. > Measured and experienced testers are vital, but end-users that are > willing to give it a go are also invaluable as they often do things in a > way that is difficult to include in regression and smoke tests. Endusers that will experience Problems during install will not likely be willing to give it a serious look. Everybody else knows about the RC anyway - be it through monitoring the mirrors, reading the releases or qa-list, some news-site mentioning it. We should not officially announce a RC that is broken. > [...] ciao Christian -- NP: Pantera - (Reprise) Sandblasted Skin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
