From owner-freebsd-stable Mon Jan 25 13:40:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15608 for freebsd-stable-outgoing; Mon, 25 Jan 1999 13:40:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.nobell.com [208.24.204.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15590 for ; Mon, 25 Jan 1999 13:40:12 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id PAA02288; Mon, 25 Jan 1999 15:39:56 -0600 (CST) (envelope-from rkw@dataplex.net) Date: Mon, 25 Jan 1999 15:39:56 -0600 (CST) From: Richard Wackerbarth To: "Ron 'The InSaNe One' Rosson" cc: freebsd-stable@FreeBSD.ORG Subject: Re: What Mailing LIST for 2.2-STABLE In-Reply-To: <19990125101153.B5527@the.oneinsane.net> 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 Yes, I think that it should exist. I also recommend a methodology to make it easy for users in the future. Call the lists "2.2", "3", "HEAD", etc. rather than "stable" and "current". Make "stable" and "current" aliases to the appropriate lists. (I think that I 'sold' Jordan on this strategy for the archives) As we approach the next branch, create a list "4" which gets the same messages as "HEAD" (automaticly cross-posted). Send out a message to everyone on the list which (by appropriate reply) moves them from "HEAD" to "4" if they so desire. When the HEAD/4 split occurs, the lists are also split and the process repeats. On the other end, the 1.x, 2.0, etc. lists can be merged into one "UNSUPPORTED" list by merging the lists and playing with the aliases. The aliases can be phased out by an auto-responder that reminds to sender that the name they are using has been deprecated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message