From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 4 17:39:21 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C6E6E5D7 for ; Wed, 4 Jun 2014 17:39:21 +0000 (UTC) Received: from mail.westryn.net (mail.westryn.net [199.48.135.251]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A887E2C08 for ; Wed, 4 Jun 2014 17:39:21 +0000 (UTC) Received: from [172.20.10.2] (116.sub-70-196-7.myvzw.com [70.196.7.116]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.westryn.net (Postfix) with ESMTPSA id 84CCD94362D; Wed, 4 Jun 2014 11:33:17 -0600 (MDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: There is currently no usable release of FreeBSD. From: Kim Shrier In-Reply-To: <332D72DF-2225-40E2-B246-0786181AAB51@tony.li> Date: Wed, 4 Jun 2014 12:33:24 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <87E37241-F2C0-46A1-9FC5-6DEE7AAAABD8@westryn.net> References: <332D72DF-2225-40E2-B246-0786181AAB51@tony.li> To: FreeBSD Hackers , John Kozubik X-Mailer: Apple Mail (2.1878.2) 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 17:39:21 -0000 On Jun 4, 2014, at 12:18 PM, Tony Li wrote: >=20 > What=92s the problem with using =91legacy=92? >=20 > Tony >=20 > On Jun 4, 2014, at 9:52 AM, John Kozubik wrote: >=20 >>=20 >> freebsd.org website shows the following: >>=20 >> Production: 10.0 >> Legacy: 9.2, 8.4 >> Upcoming: 9.3 >>=20 >> You can't put an x.0 release into production (a bigotry that is *well = deserved* in light of 5.0 and 9.0) ... and 9.2 and 8.4 are legacy ... = and we all know that 9.3 is as far as the 9 branch is going to go, so = that's a dead end for any serious deployment. >>=20 >> Let's pretend for a moment that you are going to use FreeBSD for = something other than FreeBSD development. Let's pretend that you have = customers and shareholders and boardmembers and contracts and = regulators. >>=20 >> Which version of FreeBSD would you use ? >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" If I was putting together a production system today, I would use 9.2 p7. = When 9.3 comes out, I would upgrade to it after evaluating it. Even though 9.3 = is the end of the 9.x line, it will still be supported for 3 years after it comes = out. 10.0 is a big enough change that I would hold off until 10.2 before = using it unless I needed something in 10 that wasn=92t in 9. I typically hold off until = a x.2 release to put something in production as by that time, there are usually no = surprises. Kim