From owner-freebsd-stable Tue Mar 21 16:51:46 2000 Delivered-To: freebsd-stable@freebsd.org Received: from minubian.houabg.com (minubian.houabg.com [206.109.247.11]) by hub.freebsd.org (Postfix) with ESMTP id 65AAD37BB6E for ; Tue, 21 Mar 2000 16:51:41 -0800 (PST) (envelope-from dchapman@houabg.com) Received: from houcbs2.houabg.com (mailhost.houabg.com [206.109.247.20]) by minubian.houabg.com (8.8.8/8.8.8) with ESMTP id TAA09977 for ; Tue, 21 Mar 2000 19:40:06 -0600 (CST) (envelope-from dchapman@houabg.com) Received: from 216-118-21-147.pdq.net by houcbs2.houabg.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1457.7) id GP4JPBAY; Tue, 21 Mar 2000 18:58:47 -0600 Message-ID: <010201bf9399$21158100$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Randall Hopper" Cc: 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> <20000321194509.A1273@ipass.net> Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Date: Tue, 21 Mar 2000 18:54:07 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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" To: "Brad Knowles" Cc: ; 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 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-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