From owner-freebsd-stable Wed Feb 5 11:22:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03645 for stable-outgoing; Wed, 5 Feb 1997 11:22:08 -0800 (PST) Received: from gateway.skipstone.com (root@GATEWAY.SKIPSTONE.COM [198.214.10.129]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03627 for ; Wed, 5 Feb 1997 11:22:01 -0800 (PST) Received: from [204.69.236.50] (hotapplepie.skipstone.com [204.69.236.50]) by gateway.skipstone.com (8.7.4/8.6.9) with SMTP id NAA27892; Wed, 5 Feb 1997 13:21:51 -0600 Date: 5 Feb 97 13:21:51 -0600 Subject: RE: 2.2-GAMMA is released From: "Richard Wackerbarth" To: chad@anasazi.com Cc: freebsd-stable@freebsd.org X-Mailer: Cyberdog/2.0a2 MIME-Version: 1.0 Message-Id: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, Feb 5, 1997 12:32 PM, Chad R. Larson wrote: >> This release, modulo any final bug fixes, is what will be released as >> FreeBSD 2.2R at the end of February, the length of this GAMMA testing >> cycle being approximately 20 days. > >Could someone please tell me the process (and timing) whereby 2.2R >migrates to "stable"? > >If I keep tracking the stable tree with occasional SUP/make passes, does >my machine magically become a 2.2 somewhere along the line? This becomes somewhat problematic. First, I, among others will yell loudly if any attempt is made to declare 2.2 "stable" before it has had an adequate shakedown after its release and distribution. This should take some months. Within the CTM distribution system, I have addressed this by avoiding the "stable" target name and instead using "2.1" and "2.2" to reference the particular distributions. Just as Jordan is now using a symbolic link to reference the 2.2-gamma distribution, I advocate that stable similarly become a pseudo target. That way individuals can choose when they wish to transition from 2.1 to 2.2 or can expect a massive update to occur at some unpredictable time when the link is properly moved to reflect the status of the 2.2 release.