From owner-freebsd-stable Mon Oct 6 11:39:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA18424 for stable-outgoing; Mon, 6 Oct 1997 11:39:46 -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 LAA18407 for ; Mon, 6 Oct 1997 11:39:37 -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 NAA02976; Mon, 6 Oct 1997 13:39:14 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Oct 1997 13:39:02 -0500 To: Murray Stokely From: Richard Wackerbarth Subject: Re: Fwd: CVSup release identity Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Mon, 6 Oct 1997, Richard Wackerbarth wrote: >% Well, I would still get rid of the "-STABLE". I would also use Zulu time >% and convert it all to a number. Thus > >Then what about -CURRENT?! -STABLE needs to stay there. No, it does not! The "current" branch is presently called "3.0". As far as distinguishing the versions of 2.2 which preceeded the initial release, whatever naming convention we use to distinguish later versions can be applied. For example, were we to have used the ctm delta numbers, as I recall, they were above 0100 when the 2.2.0 release happened. I can see the argument that designating the head of the development tree as 3.0 is premature. That designation probably should not have been applied until there was an actual development branch created. However, since it is likely that everything presently going into the tree will be included in 3.0, I don't think it hurts. Perhaps we should revisit this just before we split the next development branch. At that time we might want to apply a name to the development head which will not become obsolete. However, using "4.0" for the next year or so would also work. Richard Wackerbarth