Date: Tue, 21 Mar 2000 19:45:09 -0500 From: Randall Hopper <aa8vb@ipass.net> To: Brad Knowles <blk@skynet.be> Cc: stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <20000321194509.A1273@ipass.net> In-Reply-To: <v04220803b4fcf1e15773@[195.238.1.121]>; from blk@skynet.be on Tue, Mar 21, 2000 at 10:41:07AM %2B0100 References: <200003191838.KAA40955@rah.star-gate.com> <000701bf91d5$4aebeb60$0304020a@NENYA> <001a01bf91c1$7f62a4b0$0304020a@NENYA> <200003191838.KAA40955@rah.star-gate.com> <20000319220453.A65973@ipass.net> <005d01bf9221$4660ac60$0304020a@NENYA> <20000320153429.A1373@ipass.net> <v04220803b4fcf1e15773@[195.238.1.121]>
next in thread | previous in thread | raw e-mail | index | archive | help
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 where 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? Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000321194509.A1273>