From owner-cvs-all Sun Sep 13 21:32:10 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21330 for cvs-all-outgoing; Sun, 13 Sep 1998 21:32:10 -0700 (PDT) (envelope-from owner-cvs-all) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21319 for ; Sun, 13 Sep 1998 21:32:05 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA07271 for ; Sun, 13 Sep 1998 21:32:06 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Date: Sun, 13 Sep 1998 21:32:05 -0700 Message-ID: <7263.905747525.1@time.cdrom.com> From: "Jordan K. Hubbard" Subject: 2nd Heads up! Start of 3.0-BETA in 48 hours. MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To: undisclosed-recipients:; ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message To: current@freebsd.org Subject: 2nd Heads up! Start of 3.0-BETA in 48 hours. Date: Sun, 13 Sep 1998 21:32:05 -0700 Message-ID: <7263.905747525@time.cdrom.com> From: "Jordan K. Hubbard" At 23:00 PST, September 15th, the 3.0-CURRENT branch will enter BETA status and code freeze in preparation for the 3.0-RELEASE which will follow one month later on October 15th. What "code freeze" means to you: 1. No major features will be accepted, though important bug fixes to major subsystems will be if and when good cases can be made for their inclusion (we'd still like to avoid the old "fix one thing and break two others" scenario, however). In cases where something important has been dropped on the floor purely due to developer negligence, and it's not perceived as a significant risk to bring it in (e.g. a new driver or changes to a non-mission-critical subsystem), extentions may be granted on a case by case basis. Please talk to me or someone else in core if you have such a situation. 2. Changes to code should be limited to bug fixes or security enhancements. Changes to docs, since they're not quite so much on the critical path, are allowed a somewhat wider mandate here and, provided that they do not break the www or doc builds, can occur right up to the last minute (more or less). People should take special care to review release notes, the handbook or FAQ documents for references which may be obsolete or unclear with the release of 3.0. If we don't fix it now, it probably won't be fixed for the release! 3. If you observe any serious dysfunction with the 3.0-CURRENT tree after the start of BETA, please let us know immediately! Don't just wait until the last moment to test things and say "Oh no, you can't do 3.0-RELEASE yet! The Fooble driver is *totally broken*!!" Given people's propensity for waiting until the last minute with every other release, and the fact that 3.0-RELEASE is already extremely delayed as it is, I'm just as likely to say "that's a real bummer, yes, but you Fooble users should have said something earlier! Your request for an extention is denied" this time. In order to prevent such an unfortunate situation from happening, therefore, you're all just going to have to USE THESE 30+ DAYS MORE EFFECTIVELY THAN THAT! THANK YOU! :-) I also understand full well that testing is being made a bit more difficult than usual at the moment due to the large number of changes to whack into the tree in a relatively short period (ELF, Perl5, CAM). I can only say that I and others are working as fast as we can to get the release SNAPshots building on current.freebsd.org again and will certainly continue to press for things to get fixed which are holding up the show. I hope that the current ``make release'' failures will not last much beyond the start of BETA, if even that long. As usual, if you have any questions about what should go in and what should stay out, simply ask me. As the release engineer, I will have the final say in this process but also certainly intend to confer extensively with core and other developers where such issues are unclear. Here's to a great 3.0-RELEASE! - Jordan ------- =_aaaaaaaaaa--