From owner-freebsd-current Mon Aug 27 14:58:20 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 7DD5437B406 for ; Mon, 27 Aug 2001 14:58:11 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f7RLvns40398; Mon, 27 Aug 2001 17:57:49 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010827134902.A80313@rand.tgd.net> References: <3B89DF04.F6A250F9@elischer.org> <66544.998934042@critter> <20010827133112.B79584@rand.tgd.net> <3B8AB039.7090705@yahoo.com> <20010827134902.A80313@rand.tgd.net> Date: Mon, 27 Aug 2001 17:57:46 -0400 To: Sean Chittenden , Jim Bryant From: Garance A Drosihn Subject: Re: Headsup! KSE Nay-sayers speak up! Cc: Poul-Henning Kamp , Julian Elischer , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 1:49 PM -0700 8/27/01, Sean Chittenden wrote: > > > If there are grave concerns about having KSE and SMPng in > > > 5.X, then why not push back the release date? The value far > > > outweighs the extra months needed to get it finished and out > > > the door, ...etc... > > >> Good idea. > > Seriously, is there any reason to hold to a time line >at the expense of some very important and very fundamental >enhancements to FreeBSD? I suppose that's something for -core >to talk about/discuss, but I bet that if a poll was put on the >homepage of FreeBSD.org (hint hint) asking about this, you'd >get an overwhelming response to see KSE/SMPng in 5.X. With a >poll you might even pick up some more testers given the exposure >(hint hint). -sc We can't just keep pushing back the release date because "some very important enhancements" could be made. It will ALWAYS be true that there are more "very important enhancements" on the horizon, and you can't keep running after those. You have to pick some point, and stick to that point, and "ship" at that point. As long as current is known to be in rapid flux, most people WILL stay away from it. And as long as most people DO stay away from it, it will always be shaky, and it will also be tempting to add "just one more thing" to justify the delays you have already chalked up. That, in turn, causes more delays. One might call this "The Copland Effect", where you're so busy adding new stuff that you never get to a shipping product... You can not claim to be "kicking Linux's butt" (or anyone else's butt) if your product is not actually "fit for production use", which is to say, "released". I would very much like to see the KSE work in "5.0", but I still would rather delay that for a later release instead of delaying "5.0" for another three or four months. Just MO. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message