On Mon, 12 Jul 2021 01:11:42 -0600
Chris Murphy <lists(a)colorremedies.com> wrote:
You might ask in #fedora-kernel but my two cents is I generally
don't
file bugs on rawhide kernels in the RHBZ. Instead I try to figure out
what part of the kernels is blowing up, and use a current version of
the MAINTAINERS file [1] to figure out where to send an email: I'm
expecting X, I'm seeing Y, here's a dmesg. In short.
There's a ton of changes happening in the rc0 kernels, they aren't
release candidates yet. The merge window just closed, and it's 7-8
weeks of stabilization. You can expect to be asked to bisect if it
sounds like a regression; and to test a patch. If you can't, just say
so.
Branch is in about 4 weeks [2]. We will see current rawhide become
Fedora 35, which looks like it'll be kernel 4.14-rc5 by then. Any sort
of show stopper type bugs I'll file in RHBZ with a URL pointing to the
email I started with the upstream maintainers of the problem driver or
kernel component. That's because these bugs are potentially release
blocking bugs that'll need to get fixed before either the beta or
final milestone. And for that I use the blockerbugs app [3] to propose
it.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/M...
[2]
https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
[3]
https://qa.fedoraproject.org/blockerbugs/propose_bug