From owner-freebsd-current Thu Jan 6 18:20:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 4E70314EFC for ; Thu, 6 Jan 2000 18:20:42 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA14061; Thu, 6 Jan 2000 19:16:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA81656; Thu, 6 Jan 2000 19:16:03 -0700 (MST) Message-Id: <200001070216.TAA81656@harmony.village.org> To: Peter Jeremy Subject: Re: 4.0 code freeze scheduled for Jan 15th Cc: Steve Ames , current@FreeBSD.ORG In-reply-to: Your message of "Fri, 07 Jan 2000 10:16:25 +1100." <00Jan7.101628est.40323@border.alcanet.com.au> References: <00Jan7.101628est.40323@border.alcanet.com.au> <38746AEC.167EB0E7@elischer.org> <20000106094511.A30328@virtual-voodoo.com> Date: Thu, 06 Jan 2000 19:16:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <00Jan7.101628est.40323@border.alcanet.com.au> Peter Jeremy writes: : 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). This was my understanding as well... Don't feel bad. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message