Date: Thu, 6 Jan 2000 15:20:26 -0500 From: Steve Ames <steve@virtual-voodoo.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: scanner@jurai.net, Darren Reed <darrenr@reed.wattle.id.au>, Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>, louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106152026.A98222@virtual-voodoo.com> In-Reply-To: <200001062012.MAA61710@apollo.backplane.com>; from Matthew Dillon on Thu, Jan 06, 2000 at 12:12:01PM -0800 References: <Pine.BSF.4.21.0001061501001.70450-100000@sasami.jurai.net> <200001062012.MAA61710@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> We are not going to repeat the 3.0 mess. IPV6 and IPSEC are important, > but not important enough to delay the already-delayed 4.0 release. 4.1 > is not too late for these babies. True... 4.1 is not too late. However a good part of IPv6 and IPSEC are already present and the primary committer has already expressed his opinion on what can and can't be done by 1/15. > On the other hand, there are *plenty* of things already in 4.0 that really > need to get out there and get a workout by a larger audience. > Delaying *them* is a big mistake. *shudder* I really, really dislike the idea of -RELEASE actually being a wide beta so that some code can get a workout. LAbel it beta and more people will use it than currently do anyway. Any reason not to release and ship a 4.0-beta? -CURRENT = development which scares people. Beta means most bugs already ironed out and looking for test by larger audience. -RELEASE should not be a beta, ever. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000106152026.A98222>