Beta means bugs, but as few bugs as you can manage. Also bugs which are out in the release should be known to a certain degree and bugs from the previous release being fixed in the subsequent release/releases. That said, As far as I can tell, 2.0.28 is beta material. Just my simple minded $0.02
On Tue, 2001-11-13 at 17:02, Greg Stein wrote: > On Tue, Nov 13, 2001 at 12:00:31PM -0800, Ryan Bloom wrote: > > On Tuesday 13 November 2001 11:28 am, William A. Rowe, Jr. wrote: > > > From: "Greg Ames" <[EMAIL PROTECTED]> > > > Sent: Tuesday, November 13, 2001 12:56 PM > >... > > > > that file, do the PITA dance with the CHANGES file, probably do a > little > > > > testing, re-roll, rename the tarballs as beta. What do others > think? I > > > > could note that this happened in the CHANGES file since I have to > mess > > > > with it anyway. > > > > > > I'd suggest that you checkout on APACHE-2_0_28, tag as > APACHE-2_0_28_ALPHA > > > for historical reasons, then we can add APACHE-2_0_28_BETA, etc. > > > > No, there is 2.0.28, period. There isn't a 2.0.28-alpha and > 2.0.28-beta > > code base. There is one 2.0.28 codebase. You could have different > versions > > if the alpha/beta distinction was in the code, but it isn't. It is > only in the tarball > > name. > > I'm with Ryan. 2.0.28 is exactly that. alpha and beta are > *designations*. > They are not code changes. > > 2.0.28 should be buildable from the label. If the CHANGES file was > modified > *outside* of that, then we have a problem. > > Ship the damned code. This is a BETA for crying out loud. We don't need > to > weasel patches in. "oh, just this one little fix." Fuck that. Beta means > bugs. Beta means that we have a list of issues for people to be > concerned > with. Beta means people may have platform-specific problems. Beta is not > GA. > > +1 on beta. Get a release out the door. Christ almighty... what's it > take > around here? The new release process was intended to get tarballs *out* > to > people. Not to be held up in a bunch of snippy little bug fix this, bug > fix > that. Ship it out with bugs. Call it alpha if it doesn't feel right. > Call it > beta if it feels good. > > If an ErrorDocument doesn't work in one case, then tell people "too bad. > don't do that". If the server dies with a particular subrequest executed > from some wonky CGI-provided SSI document, then say "get this patch." > But we > gotta get more releases out into the public's hands. > > 2.0.16 was crap. Should people really be using that? Not a chance. > > Give them 2.0.28. > > -g > > -- > Greg Stein, http://www.lyra.org/ -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: [EMAIL PROTECTED]
