ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: ksummit@lists.linux.dev
Subject: [MAINTAINERS SUMMIT] Regression tracking & fixing: current state, problems, and next steps
Date: Mon, 20 Jun 2022 15:33:08 +0200	[thread overview]
Message-ID: <db597a89-1487-6a05-e2b4-24fc27bdebdd@leemhuis.info> (raw)

[sending a copy to this list, now that the old ksummit-discuss list is
DEFUNCT, where I posted the msg already a few days ago:

This session is meant to complement the kernel summit session with the
same title I just submitted separately
). The idea is to summarize in this session what has been discussed and
agreed on in that ksummit session and further discuss issues that need
further discussion.

I used a similar model in 2017 and it seems it worked well for everyone.
What exactly will be discussed in this sessions depends on how the
kernel summit session evolves, but I expect the following topics might
need further discussion among the core maintainers (for details on any
of these points please see the kernel summit submission linked above):

 * How slow quite a few mainline regressions are resolved, as even
simple regression fixes sometimes linger in -next for weeks before being

 * Do we care that some regressions (and many bugs) reported in
bugzilla.kernel.org are never forwarded to the maintainers? And if so,
what do we want to do about it? I tried to keep an eye on things, but
that's sometimes quite time-consuming.

 * Should I track all or some regression with regzbot that were reported
by CI systems?

 * open question: Am I holding this regression tracking thingy right or
do you want me to do it differently somehow? Or is there anything else I
can do to make my regression tracking efforts more useful for maintainers?

Ciao, Thorsten

             reply	other threads:[~2022-06-20 13:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 13:33 Thorsten Leemhuis [this message]
2022-09-16  8:54 ` [MAINTAINERS SUMMIT] Regression tracking & fixing: current state, problems, and next steps Thorsten Leemhuis

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:

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

  git send-email \
    --in-reply-to=db597a89-1487-6a05-e2b4-24fc27bdebdd@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=ksummit@lists.linux.dev \


* 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;
as well as URLs for NNTP newsgroup(s).