From owner-freebsd-stable Tue Sep 30 19:32:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA10189 for stable-outgoing; Tue, 30 Sep 1997 19:32:53 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA10183 for ; Tue, 30 Sep 1997 19:32:51 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA11449; Tue, 30 Sep 1997 19:32:42 -0700 (PDT) To: Joseph Stein cc: freebsd-stable@FreeBSD.ORG Subject: Re: Final notice: 2.2 branch code freeze is coming up. In-reply-to: Your message of "Tue, 30 Sep 1997 18:43:22 PDT." <199710010143.SAA02110@shasta.wstein.com> Date: Tue, 30 Sep 1997 19:32:42 -0700 Message-ID: <11445.875673162@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That's actually a pretty good idea - I'll do that during the BETA period no matter what we decide. ;) Jordan > > 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