From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756691AbXD0ROU (ORCPT ); Fri, 27 Apr 2007 13:14:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756686AbXD0ROT (ORCPT ); Fri, 27 Apr 2007 13:14:19 -0400 Received: from hobbit.corpit.ru ([81.13.94.6]:23962 "EHLO hobbit.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756689AbXD0ROQ (ORCPT ); Fri, 27 Apr 2007 13:14:16 -0400 Message-ID: <46322F63.9000604@msgid.tls.msk.ru> Date: Fri, 27 Apr 2007 21:14:11 +0400 From: Michael Tokarev Organization: Telecom Service, JSC User-Agent: Icedove 1.5.0.10 (X11/20070307) MIME-Version: 1.0 To: Krzysztof Halasa CC: Adrian Bunk , Linus Torvalds , Linux Kernel Mailing List Subject: Re: Linux 2.6.21 References: <20070426040806.GJ3468@stusta.de> <20070426125802.GL3468@stusta.de> <20070426165950.GO3468@stusta.de> In-Reply-To: X-Enigmail-Version: 0.94.2.0 OpenPGP: id=4F9CF57E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Krzysztof Halasa wrote: [] > We've got stable series. > With KNOWN_PROBLEMS information, sysadmins can decide if they can > safely upgrade to .0 or if they have to wait for .123. Pressing > the responsible people to fix the problems in .123 (would) help > it greatly. For how long you plan to maintain 2.6.x.y -stable series for each 2.6.x release? The thing is that tehere will probably be NO .123 "revision" (with maybe the exception of 2.6.16, thanks to Adrian again). The end result is that there will be just no stable kernels *at all*. because when the next 2.6.x will start looking more or less useful due to 2.6.x.y series, there will be new 2.6.x+1, and work with 2.6.x stops... It's not the case currently, but this way ("let's fix the bugs in 2.6.x.y -stable series, don't bother releasing 2.6.x in a good shape"), we can finally come to the above situation... /mjt