* [Ksummit-discuss] [MAINTAINERS SUMMIT] Regression tracking & fixing: current state, problems, and next steps
@ 2022-06-16 12:52 Thorsten Leemhuis
0 siblings, 0 replies; only message in thread
From: Thorsten Leemhuis @ 2022-06-16 12:52 UTC (permalink / raw)
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
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?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-06-16 12:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-16 12:52 [Ksummit-discuss] [MAINTAINERS SUMMIT] Regression tracking & fixing: current state, problems, and next steps Thorsten Leemhuis
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).