Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 27 Nov 2001 12:33:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 27 Nov 2001 12:33:05 -0500 Received: from AGrenoble-101-1-1-175.abo.wanadoo.fr ([193.251.23.175]:4992 "EHLO strider.virtualdomain.net") by vger.kernel.org with ESMTP id convert rfc822-to-8bit; Tue, 27 Nov 2001 12:32:53 -0500 Message-ID: <3C03CF2A.5070307@wanadoo.fr> Date: Tue, 27 Nov 2001 18:36:42 +0100 From: =?ISO-8859-15?Q?Fran=E7ois?= Cami User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 X-Accept-Language: en-us, fr MIME-Version: 1.0 To: Dan Kegel Cc: "linux-kernel@vger.kernel.org" Subject: Re: Kernel Releases In-Reply-To: <3C03CC6C.DD03CDDE@kegel.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Dan Kegel wrote: > 2.4.x should continue to use -preY. > There's no need for a -rcY as some have suggested. > All we need to do to avoid messes like the 2.4.15 debacle > is to insist that a 2.4.X-preY should not be > released as final 2.4.X until the pre's been out for a week, > and there should never be any changes introduced into a final > that didn't cook for a week as a pre. I don't see the difference between a -rc that has cooked for a week, and a -pre that has cooked for a week, except that -rc sounds more like "this is *maybe* the next stable kernel", whereas -pre still sounds "beta". That said, I think the week long delay is a *good* idea. Fran?ois - 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/