From: Thorsten Leemhuis <linux@leemhuis.info>
To: "ksummit@lists.linux.dev" <ksummit@lists.linux.dev>
Subject: [MAINTAINERS SUMMIT] Regressions tracking: quick state of the union & general feedback session
Date: Sat, 22 Jun 2024 18:55:21 +0200 [thread overview]
Message-ID: <fa806468-17c5-4b65-8a1e-4509d4ed6ea5@leemhuis.info> (raw)
Lo! I'd like to give a ~five minute "state of the union" talk about
regression tracking and then move over to a discussion about my work.
Yes, the maintainers summit is not for presentations; and yes, I
submitted a talk about regressions and tracking them for the kernel
summit already. But not everyone will be at the latter, which likely
includes Linus. So to better understand what he wants it might be wise
to bring the important bits up here for discussion, too. The mostly
private environment also allows sharing feedback in both directions more
openly. From what I see on the ksummit list I feel there is some
interest in a general discussion about my regression tracking efforts, too.
The talk part would cover the following things:
(a) My view on how well regressions are handled from the overall
perspective.
(b) Which subsystems from my point of view are doing a great job and
what sets them apart.
(c) The state of my regression tracking work and its future.
During the last point this would slowly morph into a more discussion
style approach, to gather feedback on how maintainers want regression
tracking to work in the bright new bugzilla+bugbot+bugspray future that
Konstantin is working on (which hopefully will improve the state of bug
handling in bugzilla, which from my point of view is about as
unsatisfying as it was two years ago when we had a big discussion about
it). Discussing the implications at least briefly seems wise, as those
improvements will lead to questions like "should regzbot be rebuilt on
top of that or does it even become obsolete?".
And there is one more thing we could use this slot for:
(d) Give everyone a chance to provide feedback to me or discuss my
efforts in general.
Ciao, Thorsten
reply other threads:[~2024-06-22 16:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fa806468-17c5-4b65-8a1e-4509d4ed6ea5@leemhuis.info \
--to=linux@leemhuis.info \
--cc=ksummit@lists.linux.dev \
/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