From owner-freebsd-current Thu Jan 6 6:50:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id A698815618; Thu, 6 Jan 2000 06:50:10 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id PAA04595; Thu, 6 Jan 2000 15:50:04 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id PAA06428; Thu, 6 Jan 2000 15:49:45 +0100 (CET) (envelope-from andreas) Date: Thu, 6 Jan 2000 15:49:45 +0100 From: Andreas Klemm To: Brad Knowles Cc: Donn Miller , Julian Elischer , Darren Reed , Yoshinobu Inoue , louie@TransSys.COM, committers@FreeBSD.org, current@FreeBSD.org Subject: Re: 4.0 code freeze scheduled for Jan 15th Message-ID: <20000106154945.A5887@titan.klemm.gtn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Thu, Jan 06, 2000 at 12:55:06PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 12:55:06PM +0100, Brad Knowles wrote: > More releases more often are better than indefinitely holding up > releases waiting for just that one last thing to be finished. Second that. And to follow on that... FreeBSD 4.0 will become the new STABLE. So 4.0 should become as stable as possible. I think there are certainly many people running on FreeBSD 2.x and 3.x who wait for something like 4.0 to become a new stable release. So we should get them the new STABLE toy ! In that short timeframe this can only be achieved by not including too much new technology into it. Otherwise we label something as STABLE which is in fact something like a -current with respect to IP V6 and IPSec. Additionally it gives developers and customers time to breath. IP V6 and IPSec should be integrated into the new 5.0(?)-current. With FreeBSD-4.0-RELEASE we will get a rapidly growing user base for 4.0 and we'll certainly have enough to do to make it really stable for everybody. In the meantime people have their new testbed in 5.0-current. If the dust has setteled in -current, I'd vote to merge IP V6 and IPsec with as much client tools as possible into something like 4.1-RELEASE. 4.0-STABLE I'd personally not touch with any brand new network code. So people have a chance to remain some time on 4.0-RELEASE or 4.0-STABLE. Another possibility would be to wait until the dust settles after merging IP V6 and IPsec into -current and release FreeBSD 4.0 complete with that features at a later time (+1-2 months). But that's probably not wanted... What do you think of that ?! Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message