From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 4 20:14:42 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F87F564; Wed, 4 Jun 2014 20:14:42 +0000 (UTC) Received: from systemdatarecorder.org (ec2-54-246-96-61.eu-west-1.compute.amazonaws.com [54.246.96.61]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "localhost", Issuer "localhost" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 38C202B83; Wed, 4 Jun 2014 20:14:41 +0000 (UTC) Received: from nereid (84-253-211-213.bb.dnainternet.fi [84.253.211.213]) (authenticated bits=0) by systemdatarecorder.org (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id s54KDksR004993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 4 Jun 2014 20:13:46 GMT Date: Wed, 4 Jun 2014 23:14:32 +0300 From: Stefan Parvu To: Jonathan Anderson Subject: Re: There is currently no usable release of FreeBSD. Message-Id: <20140604231432.a5581f5a50f8d7e1611f9736@systemdatarecorder.org> In-Reply-To: <538F5FB5.9060008@FreeBSD.org> References: <332D72DF-2225-40E2-B246-0786181AAB51@tony.li> <538F5FB5.9060008@FreeBSD.org> Organization: systemdatarecorder.org X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Tony Li X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 20:14:42 -0000 > Is the problem actually that we're using the term "legacy", which some > vendors use to mean "unsupported"? Perhaps we ought to say: better approach: stable: 8.4, 9.2, 10.0 current: 11.0 It should be clear listed what are the stable releases, can be many, and what are the future releases as well. Simple keep two naming conventions for whats stable and ready for production and what is coming next. -- Stefan Parvu