[TECH TOPIC] Regressions & tracking them: current state, plans, and what do you want?

[submitted this proposal to lpc.events a few days ago already and
posting it only now, as I was a few days afk]

Provide a quick "state of the union" about the Linux kernel regression
ecosystem in the first part of the session before spending the second
discussing what improvement the members of the audience wish for in this
area.

The first part is meant to take less then half of the allotted time and
will cover things like:

* KernelCI and regzbot joined forces -- what this means for the future.
* Tracking regressions with regzbot, the regression tracking bot: status
and future plans.
* Linux development workflow patters that lead to regressions or delay
resolving them.
* Brief "what to do and what not" when reporting regressions.

The second half will be audience driven and might discuss details in the
areas raised earlier, things like the following, or whatever the
audience is interested it:

* Regression tracking with regzbot still useful in the age of AI?
* How to improve interaction with parties interested in the space of CI,
regressions, and tracking them – like kernel maintainers of distros that
regularly update their kernels to latest stable or longterm series.
* Related: Is there interest in trees with "pending" and "wip"
regression fixes?

In case I'm invited to the kernel maintainers summit I'll also collect
topics with regards to regressions the audience wants me to bring up at
kernel maintainer summit a few days later.