From owner-freebsd-current Mon Mar 17 07:03:47 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13912 for current-outgoing; Mon, 17 Mar 1997 07:03:47 -0800 (PST) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA13880; Mon, 17 Mar 1997 07:03:41 -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 JAA08093; Mon, 17 Mar 1997 09:03:21 -0600 (CST) X-Sender: rkw@shrimp.dataplex.net Message-Id: In-Reply-To: <332D470C.41C67EA6@satech.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Mar 1997 09:01:20 -0600 To: Matthew Thyer 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 Matthew Thyer writes: >This is ridiculous. > >FreeBSD 3.X is CURRENT! It is equally correct to say -- 2.2 is the current release. 3.x is currently under development. It all boils down to the semantic interpretation. For those "in the know" we could call the head of the development tree "Rapsody" or "Bliss" or "Danger" or "Development" or "3.0" or any other code name. For those who do not "know", "current" is misleading because they typically want the "CURRENT RELEASE". This really has absolutely no relation to the buildability (or lack thereof) of the head development branch.