From owner-freebsd-stable Mon Oct 6 14:47:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA01863 for stable-outgoing; Mon, 6 Oct 1997 14:47:58 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA01855 for ; Mon, 6 Oct 1997 14:47:54 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [204.69.236.50] (GATEWAY.SKIPSTONE.COM [198.214.10.129]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id QAA08137; Mon, 6 Oct 1997 16:47:44 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <971006161539_1833122661@emout16.mail.aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 16:47:39 -0500 To: Hetzels@aol.com From: Richard Wackerbarth Subject: Re: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hetzels@aol.com writes: >In a message dated 97-10-06 14:28:35 EDT, chad@freebie.dcfinc.com writes: > >> > Well, I would still get rid of the "-STABLE". I would also use Zulu time >> > and convert it all to a number. Thus >> > >> > "FreeBSD 2.2 (9710050245)" > >I would keep the CURRENT & STABLE tags. As some one has mentioned, how can >you know if they are running CURRENT or STABLE. What difference does it make? You are running 2.2 as of (whenever). To NAME a system on the basis of its STATUS is bogus. Nothing magic happened to the 2.2 code when someone decided to declare it "STABLE". Just one update earlier, it was just as stable. Further, declaring 2.2 "STABLE" did not make 2.1 go away. It is still around. IMHO, people should think of "STABLE" as an alias to conveniently find the most current system to have reached that level of maturity. Once they have selected some system, they no longer should care what level of maturity it has reached. The system either works for them or it does not. Having anyone place a label on it is not going to affect that. BTW, by the time that 3.0 goes BETA, I expect our great team of developers to already be working on features that did not make the 3.0 cut. "CURRENT" (although I would prefer a different name) will belong to this new development. We all know that there will have to be some time between the time that 3.0.0-RELEASE comes out and the time that it can, in good faith be declared "STABLE". What are you going to call the first update after 3.0.0-RELEASE? Richard Wackerbarth