From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Oct 2002 12:05:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Oct 2002 12:05:22 -0400 Received: from dial249.pm3abing3.abingdonpm.naxs.com ([216.98.75.249]:56992 "EHLO ani.animx.eu.org") by vger.kernel.org with ESMTP id ; Mon, 21 Oct 2002 12:05:18 -0400 Date: Mon, 21 Oct 2002 12:20:16 -0400 From: Wakko Warner To: "Calin A. Culianu" Cc: linux-kernel@vger.kernel.org Subject: Re: [OT] Please don't call it 3.0!! (was Re: The reason to call it 3.0 is the desktop (was Re: [OT] 2.6 not 3.0 - (NUMA))) Message-ID: <20021021122016.A1580@animx.eu.org> References: <15786.28159.854350.479513@laputa.namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Calin A. Culianu on Mon, Oct 21, 2002 at 11:36:25AM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > So what's the verdict? Are we calling it 3.0 or 2.6? Who am I to say > this, but I really feel calling it kernel 3.0 is not fully justified. We > should stick with the 2.x series until major ABI or API changes break the > C library in massive ways, at which point we increment the major version > number. > > Although its tempting to appeal to the mainstream by inflating the version > number artificially (what's Redhat up to now? 8.0?? sheesh!!), we have to > respect ourselves as developers. Why call it 3.0, other than to stroke > our own egos? what about when they jumped from 1.3.x to 2.0.x? I suggested around the pre 2.4 days it be called 3.0 becuase of that jump there. IIRC it was slackware that jumped to be versioned up there with redhat. There've only been 2 major releases. -- Lab tests show that use of micro$oft causes cancer in lab animals