From owner-freebsd-hackers Mon Apr 14 13:52:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA13620 for hackers-outgoing; Mon, 14 Apr 1997 13:52:44 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA13613 for ; Mon, 14 Apr 1997 13:52:40 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA19230; Mon, 14 Apr 1997 13:29:06 -0700 From: Terry Lambert Message-Id: <199704142029.NAA19230@phaeton.artisoft.com> Subject: Re: Commercial vendors registry To: dennis@etinc.com (dennis) Date: Mon, 14 Apr 1997 13:29:05 -0700 (MST) Cc: terry@lambert.org, scrappy@hub.org, pgiffuni@fps.biblos.unal.edu.co, hackers@freebsd.org In-Reply-To: <3.0.32.19970412185325.00b30650@etinc.com> from "dennis" at Apr 12, 97 06:53:28 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >> There's too much "its fixed in -current" or "it'll be in the next release" > >> and not enough commitment to getting fixes and important new feature > >> into the short-term. > >But "important new features"? No way... a new feature waits for > >a release. Releases are *defined* by a feature freeze. Add a > >new feature, and once again, you have a -current. > > I said "short-term", which implied 2.3, not 3.0 in 1998. I am not happy with the release schedule, either. But: #ifdef NEW_FEATURE #define NEW_RELEASE #endif And that's the way the world works. Probably you really want more frequent releases. But then, that eaxcerbates the interface problems, as long as kernel internals are herniated out through libkvm. 8-(. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.