From owner-freebsd-current  Wed Apr 21 19:29:39 1999
Delivered-To: freebsd-current@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 3F65F1585A
	for <freebsd-current@FreeBSD.ORG>; Wed, 21 Apr 1999 19:28:07 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA46335;
	Wed, 21 Apr 1999 19:24:34 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: Doug Rabson <dfr@nlsystems.com>
Cc: Matthew Dillon <dillon@apollo.backplane.com>,
	Peter Wemm <peter@netplex.com.au>, Matthew Reimer <mreimer@vpop.net>,
	freebsd-current@FreeBSD.ORG
Subject: Re: solid NFS patch #6 avail for -current - need testers files) 
In-reply-to: Your message of "Wed, 21 Apr 1999 20:50:15 BST."
             <Pine.BSF.4.05.9904212046460.85882-100000@herring.nlsystems.com> 
Date: Wed, 21 Apr 1999 19:24:34 -0700
Message-ID: <46333.924747874@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> All I'm saying (I think) is that we shouldn't allow the 4.0 release cycle
> to stretch out to 2 years like the 3.0 cycle did (discounting 3.0 as a
> beta release).

No argument there - the current schedule is 12 months for 4.0.  2
years far too long and merely the result of unforseen delays and more
than a little paralysis over the issue. This caused a lot of
soul-searching in core over our development practices, hopefully
enough that we won't repeat that particular painful experience.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message