This is common practice for any operating system. Any x.0 version of any
operating system should not be used in a production system until major bugs
are found and fixed.
----- Original Message -----
From: "Randall Hopper" <firstname.lastname@example.org>
To: "Brad Knowles" <email@example.com>
Cc: <stable@FreeBSD.ORG>; <multimedia@FreeBSD.ORG>
Sent: Tuesday, March 21, 2000 6:45 PM
Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for
improving newpcm performance?)
> Brad Knowles:
> |At 3:34 PM -0500 2000/3/20, Randall Hopper wrote:
> |> From what I hear, it sounds like we need some more testing time too.
> | Yeah, we do. This is what an x.0-RELEASE is all about. The
> | However, IMO anyone using an x.0-RELEASE on a production box
> |basically gets what they deserve. This is more appropriate for
> |development/test/play boxes, ...
> |This is *why* they're getting an x.0-RELEASE out now, so that a wider
> |community of people with more unusual hardware and applications *can*
> |see it, and report the bugs back so that these problems can be fixed.
> |It has been stated many times over that -CURRENT isn't guaranteed to do
> |anything (including compile or run), except have a higher probability of
> |toasting your machine and your application.
> | If you want to play with x.0-RELEASE, you have to realize that
> |there are some rough spots and some sharp edges that have not yet
> |been detected, or if they have been detected they haven't yet been
> |dealt with. So again, you have to be prepared for the possibility of
> |being cut.
> I appreciate your response. I think we're talking the same language.
> The main new piece of information to me that you mentioned (somewhat of a
> surprise in fact) is that x.0-RELEASE is really only for
> "development/test/play" boxes (and thus really a -CURRENT) and not for
> production and user's-primary-PC boxes at home. I wasn't aware of this,
> but I appreciate you filling me in.
> In general, is this true just for the x.0-RELEASE, or for x.*-RELEASE
> x is the latest version in CMS (just as 4.x is now)? That is, what is the
> view of core on this in terms of planning a feature set and stability
> target for a -RELEASE?
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message