From owner-freebsd-stable Mon Mar 17 17:30:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA21596 for stable-outgoing; Mon, 17 Mar 1997 17:30:57 -0800 (PST) Received: from tok.qiv.com ([204.214.141.211]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA21587 for ; Mon, 17 Mar 1997 17:30:49 -0800 (PST) Received: (from uucp@localhost) by tok.qiv.com (8.8.5/8.8.5) with UUCP id TAA19920 for stable@freebsd.org; Mon, 17 Mar 1997 19:30:36 -0600 (CST) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.5/8.8.5) with SMTP id SAA00601 for ; Mon, 17 Mar 1997 18:32:28 -0600 (CST) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Mon, 17 Mar 1997 18:32:27 -0600 (CST) From: "Jay D. Nelson" To: stable@freebsd.org Subject: Re: -current and -stable mailing lists In-Reply-To: <8785.858624268@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry to add to the natter, but the naming scheme hasn't caused me any confusion at all. Unless you truly hope to get Joe 95 to consider FreeBSD (which strikes me like spitting into a 40 knot gale) I dont really care what you call the branches -- as long as something tells me what they are for. (I thought the handbook explained it quite well!) The one thing I would caution -- be sure that stable means stable. One of the reasons I am using FreeBSD is because I need to get other work done. I don't enjoy the 'patch of the day' cycle of development, nor can I afford it. The way things are has worked well for me. If 2.2 is _truly_ stable, then call it stable and move 2.1 to `legacy' or something. BTW -- I think abandoning 2.1 would be a mistake. Thanks for hearing me out. -- Jay [everything else snipped]