ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] stable kernel process automation and improvement
Date: Tue, 09 Jul 2019 17:44:13 +0200	[thread overview]
Message-ID: <2859305.DT5vN9tDxJ@kreacher> (raw)
In-Reply-To: <nycvar.YFH.7.76.1907082324440.5899@cbobk.fhfr.pm>

On Monday, July 8, 2019 11:31:45 PM CEST Jiri Kosina wrote:
> On Mon, 8 Jul 2019, Greg KH wrote:
> 
> > Well, I think the conversation will go just like it has in the past for
> > this issue:
> > 	"We need to have someone track regressions!"
> > 	"X said they would do it but they need to be paid, any company
> > 	willing to sponsor this?"
> > 	{crickets}
> 
> SUSE has actually been funding this for quite some time (back when Rafael 
> was doing it), but it's really tricky.
> 
> We of course realize it's very important long-term activity, from which 
> everybody profits.
> 
> At the same time, you need somebody who *really deeply* understands 
> everything inside and around the kernel development, otherwise you get 
> more harm and chaos than added value out of the whole excercise.
> 
> And if you have such a person (like we had Rafael), it's unlikely that 
> person would want to do that work forever, and the funding company is also 
> losing brainpower in other, more development-related areas (like PM in 
> Rafael's case) at the same time.
> 
> So it's not as simple as "hey, you, company making money on linux, go pay 
> someone to do this".
> 
> If I remember correctly (Rafael for sure would remember better), there 
> were some attempts to have the regression tracking made by someone much 
> more juniorish, but that person got of course immediately overwhelmed.

There were such attempts and yes, the people dropped the ball eventually.

Honestly, I don't agree with the idea that one person can practically track
regression on the whole kernel basis today, because there is too many potential
sources of information to follow.  You'd need to track all of the mailing lists used for
development, bug tracking systems in many places and so on.

When I was tracking regressions, it was more or less sufficient to follow the LKML,
and that was hard enough already at that time, but it is not sufficient any more (and
even the LKML itself has become much more of a fire hose since then).

The tracking of regressions, to be effective, would need to scale at least in the
same way as the development process does IMO.

  reply	other threads:[~2019-07-09 15:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03  1:35 Sasha Levin
2019-07-03 14:57 ` Laura Abbott
2019-07-05 13:54 ` Michael Ellerman
2019-07-05 14:13   ` Takashi Iwai
2019-07-05 16:17     ` Greg KH
2019-07-05 16:52     ` Sasha Levin
2019-07-05 16:41 ` Mark Brown
2019-07-05 20:12   ` Sasha Levin
2019-07-06  0:32     ` Mark Brown
2019-07-08 11:02       ` Sasha Levin
2019-07-08 11:35         ` Jiri Kosina
2019-07-08 12:34           ` Greg KH
2019-07-08 17:56           ` Sasha Levin
2019-07-08 12:37         ` Mark Brown
2019-07-08 14:05           ` Guenter Roeck
2019-07-08 14:33             ` Takashi Iwai
2019-07-08 15:10               ` Greg KH
2019-07-08 15:18                 ` Takashi Iwai
2019-07-08 18:08                 ` Sasha Levin
2019-07-08 21:31                 ` Jiri Kosina
2019-07-09 15:44                   ` Rafael J. Wysocki [this message]
2019-07-09 21:05                     ` Takashi Iwai
2019-07-09 15:21                 ` Laura Abbott
2019-07-08 14:50             ` Mark Brown
2019-07-08 15:06               ` Greg KH
2019-07-08 15:27                 ` Mark Brown
2019-07-08 18:01           ` Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2859305.DT5vN9tDxJ@kreacher \
    --to=rjw@rjwysocki.net \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox