From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 22 14:39:49 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 071A21065674 for ; Sun, 22 Jan 2012 14:39:49 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id BA48F8FC17 for ; Sun, 22 Jan 2012 14:39:48 +0000 (UTC) Received: from mr17.lnh.mail.rcn.net ([207.172.157.37]) by smtp02.lnh.mail.rcn.net with ESMTP; 22 Jan 2012 09:39:43 -0500 Received: from smtp04.lnh.mail.rcn.net (smtp04.lnh.mail.rcn.net [207.172.157.104]) by mr17.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id BHK36600; Sun, 22 Jan 2012 09:39:43 -0500 Received: from 209-6-86-84.c3-0.smr-ubr2.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.86.84]) by smtp04.lnh.mail.rcn.net with ESMTP; 22 Jan 2012 09:39:42 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20252.8109.369278.46542@jerusalem.litteratus.org> Date: Sun, 22 Jan 2012 09:39:41 -0500 To: freebsd-hackers@FreeBSD.org In-Reply-To: References: X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr17.lnh.mail.rcn.net) Cc: Subject: Re: FreeBSD has serious problems with focus, longevity, and lifecycle X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2012 14:39:49 -0000 Doug Barton writes: > > That would suggest that the end users don't really lose on features by > > delaying the new releases, since those features typically aren't ready > > anyway. > > I think "typically" is stretching it a bit here. As humans we > tend to focus our attention on the things that cause us problems, > rather than acknowledging (or even being aware of) the things > that are working well in the background. Also: how many (non-ports) developers out there remember bugs (including performance issues) that weren't triggered until the code went live? One can argue it shouldn't happen ... but it does. Robert Huff