Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 3 Jul 2002 11:31:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 3 Jul 2002 11:31:53 -0400 Received: from ns.suse.de ([213.95.15.193]:19717 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id ; Wed, 3 Jul 2002 11:31:51 -0400 Date: Wed, 3 Jul 2002 17:34:21 +0200 From: Dave Jones To: Bill Davidsen Cc: Linux-Kernel Mailing List Subject: Re: [OKS] Kernel release management Message-ID: <20020703173421.B8934@suse.de> Mail-Followup-To: Dave Jones , Bill Davidsen , Linux-Kernel Mailing List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from davidsen@tmr.com on Mon, Jul 01, 2002 at 02:25:16PM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1061 Lines: 23 On Mon, Jul 01, 2002 at 02:25:16PM -0400, Bill Davidsen wrote: > I suggested that 2.5 be opened when 2.4 came out, so I like the idea of > 2.7 starting when 2.6 is released. I think developers will maintain the > 2.6 work out of pride and desire to have a platform for the "next big > thing." And their code can always be placed on hold for 2.7 until they > clarify their thinking on 2.6, if that's really needed. Unfortunatly, there's the possibility of people thinking "I'll fix it properly in 2.7, and backport", during which time, 2.6 doesn't get fixed any faster. People diving into 2.7 development and leaving 2.6 to those that actually care about stabilising it was Linus' concern if I understood correctly at the summit. Dave -- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/