Date: Tue, 21 Mar 2000 10:41:07 +0100 From: Brad Knowles <blk@skynet.be> To: Randall Hopper <aa8vb@ipass.net>, Cameron Grant <gandalf@vilnya.demon.co.uk> Cc: Amancio Hasty <hasty@rah.star-gate.com>, Conrad Sabatier <conrads@home.com>, stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?) Message-ID: <v04220803b4fcf1e15773@[195.238.1.121]> In-Reply-To: <20000320153429.A1373@ipass.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 people seriously hacking on -CURRENT are largely done with this chunk of their work, and things have been mostly cleaned up to the point where it's semi-useable. Now, it's time to get this code out to a wider audience, and see what else is missing and needs to be fixed. 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, so that you can get a feel for what is coming, and you'll feel comfortable enough with it that by the time x.3-RELEASE comes around, you will feel confident that you can safely put it into production. > Exactly. The kernel revolves around applications. And applications > revolve around users and their needs. True enough. But the guys who've been doing some serious hacking on -CURRENT don't have all the various bits of more unusual hardware and applications that the wider community has, so they can't see these problems, and if they can't see them then they can't fix them. 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. > Sorry Fred. That line don't fly with me. I don't have to stand ready with > coding time to fix anything you want to break or rip out. If you want to play with -CURRENT, yes you do. 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. This is the true bleeding edge, and if you want to play, you have to be prepared to get cut pretty often. 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. If you prefer not to get cut, then you had better stick with the -STABLE tree, which right now means 3.x-STABLE. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, <blk@skynet.be> || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium 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?v04220803b4fcf1e15773>