From owner-freebsd-current Thu Jan 6 12: 3: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 28C08155A4; Thu, 6 Jan 2000 12:02:57 -0800 (PST) (envelope-from scanner@jurai.net) Received: from localhost (scanner@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA70527; Thu, 6 Jan 2000 15:02:33 -0500 (EST) Date: Thu, 6 Jan 2000 15:02:32 -0500 (EST) From: To: Darren Reed Cc: Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <200001060927.UAA03779@avalon.reed.wattle.id.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Jan 100, Darren Reed wrote: > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message