From owner-freebsd-stable Mon Apr 9 10:39:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.unixathome.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 2DCF437B422 for ; Mon, 9 Apr 2001 10:39:14 -0700 (PDT) (envelope-from dan@langille.org) Received: from xeon (xeon.int.nz.freebsd.org [192.168.0.18]) by ns1.unixathome.org (8.11.3/8.11.3) with ESMTP id f39Hcje73052; Tue, 10 Apr 2001 05:38:45 +1200 (NZST) (envelope-from dan@langille.org) Date: Tue, 10 Apr 2001 05:38:45 +1200 (NZST) From: Dan Langille X-X-Sender: To: "Michael R. Rudel" Cc: Christopher Schulte , Matthew Emmerton , Rasputin , 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 Mon, 9 Apr 2001, Michael R. Rudel wrote: > [... SNIP ...] > > Personally, I don't see a problem with the -CURRENT and -STABLE naming > scheme. As someone said, anybody who can CVSup (not to mention get the > sample CVSup files to work off of) yet not read the rest of the > documentation has other issues. Renaming -CURRENT to -DEV or -DEVEL would > be the equivlent of dulling all the knives in your house so that people > don't cut themselves. A poor analogy. A better one would be labelling the knife drawer something other than knives. > Changing the whole > release process of something that has worked for years isn't going to help > anything Nothing has been suggested about change the *process*. AFAIK, we're talking about the name. Not the process >, people are always going to be confused if you change it - if you > suddenly change the way this shit is named, I'm going to be confused when > 4.4 comes around or whatever. Said confusion, if any, would be temporary and well announced. What is being proposed is a name which helps new people out and which will still make sense long after they've joined te project. > Just chill, and instruct people to Read The > Fine Manual. AFAIK, everyone is chilled. As for discarding the issue with a RTFM, that's avoiding the issue altogether and will not achieve anything. Reasoned discussion, whch is what I thought we were doing, will. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message