From owner-freebsd-hackers@FreeBSD.ORG  Wed Jun  4 20:36:25 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
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 D7009290;
 Wed,  4 Jun 2014 20:36:25 +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 71A872EA2;
 Wed,  4 Jun 2014 20:36:25 +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
 s54KZUV1005081
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
 Wed, 4 Jun 2014 20:35:31 GMT
Date: Wed, 4 Jun 2014 23:36:17 +0300
From: Stefan Parvu <sparvu@systemdatarecorder.org>
To: Allan Jude <allanjude@freebsd.org>
Subject: Re: There is currently no usable release of FreeBSD.
Message-Id: <20140604233617.a97ffe3b3e04c6d8bbb2b4db@systemdatarecorder.org>
In-Reply-To: <538F7F10.7070605@freebsd.org>
References: <alpine.BSF.2.00.1406040944570.2120@kozubik.com>
 <332D72DF-2225-40E2-B246-0786181AAB51@tony.li>
 <538F5FB5.9060008@FreeBSD.org>
 <20140604231432.a5581f5a50f8d7e1611f9736@systemdatarecorder.org>
 <538F7F10.7070605@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
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jun 2014 20:36:25 -0000


> Technically, the branches are stable

fair enough, but remember some people don't know what are FreeBSD branches
nor the internal notation or the calling convention. They want to know what can 
they download to use on their production environments. As well, probable makes
sense to have somewhere defined why there are 3 stable, production releases
and the life support scheme for each.

Sort of: http://en.wikipedia.org/wiki/Solaris_%28operating_system%29
(Solaris Release Timeline)

> so it'd be:
> Releases: 10.0, 9.2, 8.4
> Testing: 11-snapshot, 9.3

Sounds good. I think legacy should be dropped in favour of something simpler and easy
to digest from sys admins to data center managers.

-- 
Stefan Parvu <sparvu@systemdatarecorder.org>