From owner-freebsd-current Thu Jan 6 15:52:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C173B14CC8 for ; Thu, 6 Jan 2000 15:52:42 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA19535; Thu, 6 Jan 2000 15:50:31 -0800 Date: Thu, 6 Jan 2000 15:50:29 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Peter Jeremy , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: 4.0 code freeze scheduled for Jan 15th In-Reply-To: <00Jan7.101628est.40323@border.alcanet.com.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 Yes, this is a very good point. Jordan, which is it? On Fri, 7 Jan 2000, Peter Jeremy wrote: > On 2000-Jan-07 01:43:09 +1100, Steve Ames wrote: > > _FEATURE_ freeze is January 15th. > > Not quite - Jordan specifically stated _CODE_ freeze (see the Subject:). > > Maybe I misunderstood Jordan's original announcement, but this was > also a surprise for me. Jordan originally stated that there'd be a > feature freeze from 15th December 1999. I got the impression that > this was going to be in effect for several months and would allow any > code updates, but prevent the introduction of new features. This > would then be followed by a _CODE_ freeze sometime in 2000Q1, leading > to 4.0-RELEASE late in 2000Q1. (My understanding of the difference is > that during the code freeze, only changes that demonstrably fix known > bugs, without deleterious side effects, are allowed). > > A few weeks ago, I saw comments that it had slipped a month, followed > a few days ago by Jordan's announcement of a code freeze. > > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message