From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 4 23:33:03 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 73C028DB; Wed, 4 Jun 2014 23:33:03 +0000 (UTC) Received: from kozubik.com (kozubik.com [216.218.240.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5D22020E3; Wed, 4 Jun 2014 23:33:02 +0000 (UTC) Received: from kozubik.com (localhost [127.0.0.1]) by kozubik.com (8.14.3/8.14.3) with ESMTP id s54NX1jS007156; Wed, 4 Jun 2014 16:33:01 -0700 (PDT) (envelope-from john@kozubik.com) Received: from localhost (john@localhost) by kozubik.com (8.14.3/8.14.3/Submit) with ESMTP id s54NWuEr007153; Wed, 4 Jun 2014 16:32:56 -0700 (PDT) (envelope-from john@kozubik.com) Date: Wed, 4 Jun 2014 16:32:56 -0700 (PDT) From: John Kozubik To: Poul-Henning Kamp Subject: Re: There is currently no usable release of FreeBSD. In-Reply-To: <19839.1401922026@critter.freebsd.dk> Message-ID: References: <18771.1401901640@critter.freebsd.dk> <19839.1401922026@critter.freebsd.dk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 23:33:03 -0000 On Wed, 4 Jun 2014, Poul-Henning Kamp wrote: >>>> 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. > > And that's exactly why I'd start with -current. By the time you're > ready to go live, it will be -stable. > > If you start at 8, 9 or 10 now, you'll be overdue to upgrade by the > time you go live. I agree that the releases do not last long enough to settle on and grow into. That is why we *need* a release to go into double-digit minors, like 4 did when it went to 4.11. I don't even care which one! Any of them! Just give us a release that we can grow into and not find ourselves at "legacy" two years later, at 9.2. Which, by the way, is actually a step backwards. I was appalled to find that 8 was marked legacy at 8.3, but now 9 is marked legacy at 9.2. Which means if there is some bug in 'em' or 'twa' and it gets fixed in 10, you'll never see it backported to 9. Be honest.