From owner-freebsd-stable Mon Apr 9 12:13:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id D1E3F37B424 for ; Mon, 9 Apr 2001 12:13:28 -0700 (PDT) (envelope-from freebsd@bolingbroke.com) Received: from fremont.bolingbroke.com (fremont.bolingbroke.com [216.102.90.210]) by fremont.bolingbroke.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f39JDSU47292 for ; Mon, 9 Apr 2001 12:13:28 -0700 (PDT) Date: Mon, 9 Apr 2001 12:13:28 -0700 (PDT) From: Ken Bolingbroke To: freebsd-stable@FreeBSD.ORG Subject: Re: Releases In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 10 Apr 2001, Dan Langille wrote: > On Mon, 9 Apr 101, Przemyslaw Brojewski wrote: > > > There's not such thing as self-documenting labels. > > Sure there are. You see them everyday. On example :push: on a door. I'd say that's more of an instruction than a label. But regardless of such nit-picking, even if we can think of a self-documenting label, it's going to be something simple enough to be contained within a small label. The nature of the various branches and the stages of those branches pretty much guarantee that you can't find a self-documenting label for those, because they're just too complex. (Feel free to prove me wrong, tho :-) There are different situations under which I would run -RELEASE instead of -STABLE, as well as other situations where I might run RELENG_3 instead of RELENG_4. But they're complex, requiring an understanding of each branch, their stages, and so forth. To understand which I need, it requires due process in reading the documentation and following the mailing lists. As has been said all too many times, if someone is NOT going to read the documentation, they're going to have trouble, period. Changing the labels just to delay their troubles a bit longer doesn't really help anyone. At best, if they _must_ change, I'd say change them to something totally unrelated. -STABLE becomes -MARS, -CURRENT becomes -JUPITER, etc. Having no inherent meaning would force (or am I too optimistic?) people to read the docs to find the meaning rather than making likely flawed assumptions as to what they mean. But I'd rather they not change at all. The current system _is_ logical, even if it takes a bit of time to grok it. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message