From owner-freebsd-stable Fri Oct 3 04:45:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08642 for stable-outgoing; Fri, 3 Oct 1997 04:45:49 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08611; Fri, 3 Oct 1997 04:45:28 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id EAA02871; Fri, 3 Oct 1997 04:45:00 -0700 (PDT) To: stable@freebsd.org cc: committers@freebsd.org Subject: We are now in 2.2.5 BETA test. Date: Fri, 03 Oct 1997 04:44:59 -0700 Message-ID: <2866.875879099@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday, the 2.2-stable branch (tag name: RELENG_2_2) transitioned to BETA status for the upcoming 2.2.5 release on the 20th of October. Daily snapshots of the 2.2-stable branch continue to be made on ftp://releng22.freebsd.org/pub/FreeBSD, though each release is now titled 2.2.5-YYMMDD-BETA instead of the usual 2.2-YYMMDD-RELENG during this testing period. These snapshots should now essentially be considered a "floating BETA", each new tester being expected to install the latest one available (and some number of these snaps will also be mirrored at ftp.freebsd.org during the BETA cycle) and reporting whatever bugs they find in it so we can fix them for the next 24 hour period. It is my hope that this slightly different model of BETA testing will allow us to converge more quickly on a quality 2.2.5 release, these daily snapshots (hopefully) also helping to make sure that nothing gets broken at the last minute. We are now also in code freeze for the 2.2-stable branch, code freeze meaning that the riskier areas of the system (primarily the kernel and some of the more "core" utilities) are strictly off-limits and you need to talk to me first before contemplating any serious changes in those areas. Straight-forward bug fixes and non-critical changes (e.g. to things like docs) are fine, as are some of the "this has worked for ages in -current and somebody simply forgot to bring it over!" sorts of things. I don't mean to sound too permissive during a code freeze, and if you break the tree I *will* yell at you, but that latter category is actually something of a worry since there really is a *lot* of stuff which constitutes some simple and obvious bug fix or enhancement and really should have been brought over before now, but everyone simply missed it in the rush. There's so much of this kind of stuff that I really wouldn't mind some of it making it in if it could also happen in the very earliest days of the BETA (noting the "critical section" rule I stated before, obviously) so we could still get some adequate testing in for it. Otherwise there's always 2.2.6, so don't get cocky and push the envelope, either. ;) Release of 2.2.5 is scheduled for the 20th of October. I'll also be making the CD release for this a 4 CD set (finally!) so we'll have a pretty good collection of stuff available. It should be a good release if we can put the next 17 days to good use. Test away, ladies and gentlemen! :-) Jordan