From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760094AbXKHNiZ (ORCPT ); Thu, 8 Nov 2007 08:38:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756492AbXKHNiP (ORCPT ); Thu, 8 Nov 2007 08:38:15 -0500 Received: from hawking.rebel.net.au ([203.20.69.83]:33247 "EHLO hawking.rebel.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754198AbXKHNiP (ORCPT ); Thu, 8 Nov 2007 08:38:15 -0500 Message-ID: <4733113E.4090806@davidnewall.com> Date: Fri, 09 Nov 2007 00:08:06 +1030 From: David Newall User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: ciol CC: linux-kernel@vger.kernel.org Subject: Re: [poll] Is the megafreeze development model broken? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org ciol wrote: > * Do you think the megafreeze development model [1] and the "I don't > trust in upstream" development model are broken? (And why) I'm new to LKML, and because this is "my first release" I've held off saying that the development model scares me. No doubt I need to see it through a couple of releases, minimum. If I was less sanguine I might say something about how often "this is tested and ready to be pushed upstream" presages "the system is broken and doesn't work." I think if most CIOs monitored the list they'd never let Linux anywhere near their business systems. It's scary!