From owner-freebsd-stable Mon Mar 17 10:27:46 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA25243 for stable-outgoing; Mon, 17 Mar 1997 10:27:46 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA25233; Mon, 17 Mar 1997 10:27:43 -0800 (PST) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.8.5/8.6.6) with ESMTP id LAA07384; Mon, 17 Mar 1997 11:25:54 -0700 (MST) Message-Id: <199703171825.LAA07384@rover.village.org> To: ac199@freenet.hamilton.on.ca Subject: Re: -current and -stable mailing lists Cc: Richard Wackerbarth , Matthew Thyer , current@freebsd.org, stable@freebsd.org In-reply-to: Your message of "Mon, 17 Mar 1997 10:43:38 EST." References: Date: Mon, 17 Mar 1997 11:25:54 -0700 From: Warner Losh Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message Tim Vanderhoek writes: : I'm not sure how much interpretation is necessary. There : are three concurrent branches. -STABLE, -RELEASE, and : -CURRENT. All three of these branches are, in fact, : _current_. The problem is introduced when people confuse : "current" with -CURRENT. The -stable branch isn't very current wrt bug fixes and the like. There have been long periods of time when it was woefully neglected, and it is time to admit that it is mature, and move on to 2.2. We'll be doing our users a disservice if we keep encouraging them to use old, moldy software. Warner