From owner-freebsd-stable  Mon Feb 17 20:52:41 1997
Return-Path: <owner-stable>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id UAA16474
          for stable-outgoing; Mon, 17 Feb 1997 20:52:41 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA16468
          for <freebsd-stable@freebsd.org>; Mon, 17 Feb 1997 20:52:39 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id UAA29406; Mon, 17 Feb 1997 20:52:32 -0800 (PST)
To: chad@anasazi.com
cc: freebsd-stable@freebsd.org
Subject: Re: stable migration path 
In-reply-to: Your message of "Mon, 17 Feb 1997 19:19:44 MST."
             <9702180219.AA02973@chad.anasazi.com> 
Date: Mon, 17 Feb 1997 20:52:32 -0800
Message-ID: <29403.856241552@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
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?

No, it should track the RELENG_2_2 tag.

> What will be the migration plan as -stable becomes 2.2 and -current
> becomes 3.0?

-stable won't become 2.2 until 2.2.x (where x is at least 1 and probably
more like 2 or 3).  At that time, we'll announce cut-over plans for folks
after we've tested the upgrade picture at that time using the latest
2.1.x and 2.2.x bits.

					Jordan