Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 26 Nov 2001 15:43:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 26 Nov 2001 15:42:00 -0500 Received: from cx879306-a.pv1.ca.home.com ([24.5.157.48]:23027 "EHLO siamese.dhis.twinsun.com") by vger.kernel.org with ESMTP id ; Mon, 26 Nov 2001 15:40:09 -0500 From: junio@siamese.dhis.twinsun.com To: Marcelo Tosatti To: Alan Cox To: David Weinehall Cc: "H. Peter Anvin" , linux-kernel@vger.kernel.org Subject: Re: Release Policy [was: Linux 2.4.16 ] In-Reply-To: Date: 26 Nov 2001 12:39:34 -0800 In-Reply-To: Message-ID: <7v1yil1d2x.fsf@siamese.dhis.twinsun.com> Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>> "MT" == Marcelo Tosatti writes: MT> On Mon, 26 Nov 2001, H. Peter Anvin wrote: >> Consistency is a Very Good Thing[TM] (says the one who tries to teach >> scripts to understand the naming.) The advantage with the -rc naming is >> that it avoids the -pre5, -pre6, -pre-final, -pre-final-really, >> -pre-final-really-i-mean-it-this-time phenomenon when the release >> candidate wasn't quite worthy, you just go -rc1, -rc2, -rc3. There is no >> shame in needing more than one release candidate. MT> Agreed. I stick with the -rc naming convention for 2.4+... (This is a request to maintainers of three stable trees). While we are on the topic, could you also coordinate to keep the EXTRAVERSION strings consistent? 2.4.X-preN uses "-preN" but 2.2.X-preN uses "preN" without leading "-". - 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/