From owner-freebsd-current Wed Jan 5 11:44:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D3C6315459; Wed, 5 Jan 2000 11:44:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA28156; Wed, 5 Jan 2000 11:44:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: committers@freebsd.org Cc: current@freebsd.org Reply-To: committers@freebsd.org Subject: 4.0 code freeze scheduled for Jan 15th Date: Wed, 05 Jan 2000 11:44:06 -0800 Message-ID: <28153.947101446@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG And given that we've already slipped from December 15th, I think you can treat this as a pretty hard deadline, to be further slipped only grudgingly and in response to clear and dire need. 10 days, folks! Make 'em count.. :) The code freeze will last for 15 days, during which time the 4.0 snapshot server (current.freebsd.org) will be cranking out its daily snapshots (and, in the last half of the release cycle, ISO images as well). There will be an additional 10 days following 4.0-RELEASE before the final CD images are made, it being our goal to get the bugs worked out of the net release before the CDs are made in the future. This will result in some additional lag to CD customers, but they'll also get a product with the sharp edges filed off in return for the delay and I think it's worth-while since CDs are a lot harder to update than FTP sites. :-) If someone would care to volunteer an Alpha which has good network connectivity and enough "oomph" to create a full release every night, I'd also be happy to drag the Alpha architecture into this process of doing some actual release QA by porting my snapshot building scripts over and starting them up. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message