From owner-freebsd-current Thu Jan 6 12:12:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 26C2515737; Thu, 6 Jan 2000 12:12:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA61710; Thu, 6 Jan 2000 12:12:01 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 12:12:01 -0800 (PST) From: Matthew Dillon Message-Id: <200001062012.MAA61710@apollo.backplane.com> To: Cc: Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> For what it's worth, I think releasing 4.0 *without* IPv6 support :> is a mistake. Why ? Because in < 12 months FreeBSD 5.0 will be :> released *with* IPv6 support (I'd count IPv6 as being a big enough :> change to signify a major release number change). If that doesn't :> happen, then FreeBSD is chasing the wrong goals, IMHO. : :I would like to agree with darren on this one. And think IPv6 should go :into 4.0 even if the date needs to be pushed back. It is a major release :and adding v6 is a major change. Thats just my 2 cents anyway. : :Chris 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. 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. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message