> > At 10:42 AM 8/14/01 +0200, Michel Lehon wrote:
> > >> From: Weiqi Gao [mailto:[EMAIL PROTECTED]]
> > >> On 13 Aug 2001 22:08:50 +0000, Arved Sandstrom wrote:
> > >> > ...I suggest that we mandate a code freeze starting N days
> > >> > before the release. At the start of the freeze I build a
> > >> > distro, and it will be labelled as a pre-release (PR suffix maybe?)
> > >> > During those N days (2 days, 3 days?) everyone will have an
> > >> > opportunity to test the release, and find those bad bugs that
> > >> > somehow never showed up before.
> > >>
> > >> That sounds like a very good idea. And I have seen other Apache
> > >> projects doing it. (Except that they are not calling it
> "PR". This is
> > >> another instance where Apache management should probably
> > dictate all sub
> > >> projects to use a uniform name for the pre-releases.)
> > >
> > >How about beta releases ? like they do for Tomcat, Cocoon, ...
> > >The beta cycle would be nice for bug fixes, user feedback, and
> > integration
> > >with other projects.
> > I don't want to call these things "betas" or "alphas", since
> they aren't.
> > The purpose isn't really different, though, so I'm not
> religious over it.
> > Open-source has fuzzied the meanings up anyway.
> > The pre-release period is meant to be quite short. Weiqi points
> > out that we
> > should RERO (Release Early, Release Often); he's quite right.
> > We've tried to
> > release at least once a month, and maybe even every 2 weeks,
> without much
> > success to date. But if we were releasing once a month I
> wouldn't want to
> > see more than 3 or 4 days allocated to a pre-release code
> freeze, myself.
> I think it would be nice to have something like
> code freeze + release, lets call it CF (like code freeze)
> have one week to test it, integrate with other projects...
> do a release without the CF suffix ?
even better how about using the same convention as Xalan2
they do Developer releases just for that purpose...
Developer feedback and early user comments...
and it seems to work.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]