From owner-freebsd-stable  Tue Sep 30 18:43:40 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA07837
          for stable-outgoing; Tue, 30 Sep 1997 18:43:40 -0700 (PDT)
Received: from shasta.wstein.com (joes@shasta.wstein.com [207.173.11.132])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA07830
          for <freebsd-stable@FreeBSD.ORG>; Tue, 30 Sep 1997 18:43:34 -0700 (PDT)
Received: (from joes@localhost)
	by shasta.wstein.com (8.8.7/8.8.7) id SAA02110;
	Tue, 30 Sep 1997 18:43:23 -0700 (PDT)
From: Joseph Stein <joes@seaport.net>
Message-Id: <199710010143.SAA02110@shasta.wstein.com>
Subject: Re: Final notice:  2.2 branch code freeze is coming up.
In-Reply-To: <10635.875667912@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 30, 97 06:05:12 pm"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Tue, 30 Sep 1997 18:43:22 -0700 (PDT)
Cc: freebsd-stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31H (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> So, this all sort of raises the very obvious question and that is
> "Just what the heck is an official 2.2.5-BETA release good for if it's
> only going to be rendered essentially obsolete 24 hours later when the
> 2.2 SNAP server cranks out another full release?  Why not just point
> at the 2.2.5-971001-RELENG snapshot and say "There, that's the BETA.
> Testers, please start your engines!" 

So, you call the releases at releng22.freebsd.org

2.2.5-971001-BETA

??

My $.02

joe