From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AA0B825A for ; Sat, 9 Jul 2016 00:33:02 +0000 (UTC) Received: from cloudserver094114.home.net.pl (cloudserver094114.home.net.pl [79.96.170.134]) by smtp1.linuxfoundation.org (Postfix) with SMTP id 91B6410E for ; Sat, 9 Jul 2016 00:33:01 +0000 (UTC) From: "Rafael J. Wysocki" To: Dmitry Torokhov Date: Sat, 09 Jul 2016 02:37:40 +0200 Message-ID: <91774112.AKkGksYjl6@vostro.rjw.lan> In-Reply-To: <20160709001046.GH28589@dtor-ws> References: <5780334E.8020801@roeck-us.net> <20160709001046.GH28589@dtor-ws> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Cc: ksummit-discuss@lists.linux-foundation.org, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE TOPIC] stable workflow List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Friday, July 08, 2016 05:10:46 PM Dmitry Torokhov wrote: > On Fri, Jul 08, 2016 at 04:12:14PM -0700, Guenter Roeck wrote: > > On 07/08/2016 03:35 PM, Jiri Kosina wrote: > > >Yeah, this topic again. It'd be a sad year on ksummit-discuss@ without it, > > >wouldn't it? :) > > > > > >As a SUSE Enterprise Linux kernel maintainer, stable kernel is one of the > > >crucial elements I rely on (and I also try to make sure that SUSE > > >contributes back as much as possible). > > > > > >Hence any planned changes in the workflow / releases are rather essential > > >for me, and I'd like to participate, should any such discussion take > > >place. > > > > > > > Same here. New employer, lots of unhappiness with stable releases, to the point > > where stable trees are not used as basis for shipping releases. > > That kind of defeats the purpose. So, instead of "let's ignore stable", > > maybe we can get to a point where people feel comfortable with the quality > > of stable releases, and where stable can actually be used as basis for production > > releases. > > I wonder if it would not be a good idea to split stable into several > flavors: security, fixes to core (really fixes), and fixes to device > drivers + new hardware support. That would be sort of confusing IMO. The "one stable series per release" model is good, because it is really straightforward and it is rather hard to get things wrong within it. > I feel that with current single stable > tree (per stable release) we are too liberal with what we direct towards > stable, with many changes not being strictly necessary, but rather "nice > to have". To me, as long as they all are fixes, that's fine. I tend to think that all known bugs should be fixed, at least because once they have been fixed, no one needs to remember about them any more. :-) Moreover, minor fixes don't really introduce regressions that often (from my experience), because they tend to be simple. Significant fixes, on the other hand, tend to be more complicated or more subtle and the risk of regressions from them is so much greater. Thanks, Rafael