From owner-freebsd-stable  Mon Feb 17 20:22:20 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA14201
          for stable-outgoing; Mon, 17 Feb 1997 20:22:20 -0800 (PST)
Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA14178
          for <stable@freebsd.org>; Mon, 17 Feb 1997 20:22:07 -0800 (PST)
Received: from [208.2.87.3] (shrimp [208.2.87.3]) by eel.dataplex.net (8.7.5/8.6.9) with ESMTP id WAA20116; Mon, 17 Feb 1997 22:21:58 -0600 (CST)
X-Sender: rkw@mail.dataplex.net
Message-Id: <l03010d01af2edcff3af6@[208.2.87.3]>
In-Reply-To: <9702180219.AA02973@chad.anasazi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 17 Feb 1997 22:20:05 -0600
To: chad@anasazi.com
From: Richard Wackerbarth <rkw@dataplex.net>
Subject: Re: stable migration path
Cc: stable@freebsd.org
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I've got a couple of machines here that are using SUP to track the
>stable world (and now call themselves 2.1.7).  I just loaded up another
>one with 2.2-GAMMA.  Should it track the -current tree?
>
>What will be the migration plan as -stable becomes 2.2 and -current
>becomes 3.0?

I hope that they will create 2.1 and 2.2 targets so that you can switch to
those
long before "stable" changes.  That way, YOU will have control over the time
that you switch. After all, that 2.2 machine won't be changing just because
someone decides to bless 2.2 and call it "stable".
"current" will always basically be un-numbered because 3.0 has not been
split off of the trunk yet. And when it does, "current" will become 3.1 or 4.0
or whatever.