Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261305AbVCBXs2 (ORCPT ); Wed, 2 Mar 2005 18:48:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261273AbVCBXoD (ORCPT ); Wed, 2 Mar 2005 18:44:03 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:29878 "EHLO parcelfarce.linux.theplanet.co.uk") by vger.kernel.org with ESMTP id S261186AbVCBXm6 (ORCPT ); Wed, 2 Mar 2005 18:42:58 -0500 Message-ID: <42264F6C.8030508@pobox.com> Date: Wed, 02 Mar 2005 18:42:36 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linus Torvalds CC: Kernel Mailing List , Andrew Morton Subject: Re: RFD: Kernel release numbering References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 891 Lines: 25 IMO too confusing. And it exacerbates an on-going issue: we are moving away from "release early, release often", as this proposal just pushes the list of pending stuff back even further. Developers right now are sitting on big piles, and pushing that back even further means every odd release means you are creating a 2.4.x/2.5.x backport situation every two releases. To take a radical position on the other side, I would prefer a weekly snapshot as the release, staging invasive things in -mm. And I think -mm is not enough, even. We have to come up with new ways to manage this ever-increasing flow of data into our tree. Jeff - 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/