From owner-freebsd-current Thu Jan 6 15:24:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 24C2B1578E for ; Thu, 6 Jan 2000 15:24:14 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Fri, 7 Jan 2000 10:16:28 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: 4.0 code freeze scheduled for Jan 15th In-reply-to: <20000106094511.A30328@virtual-voodoo.com>; from steve@virtual-voodoo.com on Fri, Jan 07, 2000 at 01:43:09AM +1100 To: Steve Ames Cc: current@FreeBSD.ORG Message-Id: <00Jan7.101628est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <38746AEC.167EB0E7@elischer.org> <20000106094511.A30328@virtual-voodoo.com> Date: Fri, 7 Jan 2000 10:16:25 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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