From owner-freebsd-current Sun Mar 16 17:24:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA08876 for current-outgoing; Sun, 16 Mar 1997 17:24:40 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08866; Sun, 16 Mar 1997 17:24:37 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by who.cdrom.com (8.8.5/8.6.11) with ESMTP id QAA23869 ; Sun, 16 Mar 1997 16:26:47 -0800 (PST) Received: from [208.2.87.4] (cod.dataplex.net [208.2.87.4]) by shrimp.dataplex.net (8.8.5/8.8.5) with ESMTP id SAA14829; Sun, 16 Mar 1997 18:26:39 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <199703162206.PAA16084@rocky.mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 16 Mar 1997 18:25:21 -0600 To: Nate Williams From: Richard Wackerbarth Subject: Re: -current and -stable mailing lists Cc: current@FreeBSD.org, stable@FreeBSD.org Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Where do we send bug reports and comments on 2.2 now that 2.2 is >released? In the past -stable was 2.1.*, and -current was >anything/everything else. > >Inquiring minds would like to know? Should we state that 2.2 is now >-stable material, since I suspect it's at least as stable as the 2.1.0 >release. IMHO, we need to get away from the bifurcated view of systems. 2.2 certainly has not yet proven itself enough to be a replacement for 2.1. And, at the same time, the head branch is a different development. If we MUST use the "current" tag to refer to any system, 2.2 is an ideal candidate. I realize that there is the hysterical (historical?) precedent that calls that "not yet ready for public view" 3.0 system "current" although "future" might be more appropriate. I suggest that the best solution is to drop the status designations and instead use the release family as the designation. 2.1, 2.2, 3.0, etc. That way it is clear which list is appropriate for a particular discussion. A small change in the majordomo setup could make the change easy for the users. The mailing list for "stable" and traffic to it could be rerouted to a new 2.1 list. The "current" list could be duplicated into both the 2.2 and 3.0 lists. As people learn to direct traffic to a more specific list, the old lists could be phased out. Until someone decides to change something in the mailing lists, I recommend that things remain as they were. "stable" is 2.1. "current" is anything more recent. However, "[2.2]" or [3.0]" in the subject would help sort things.