From: Konstantin Ryabitsev <email@example.com>
To: Thorsten Leemhuis <firstname.lastname@example.org>
Cc: Krzysztof Kozlowski <email@example.com>,
Linus Torvalds <firstname.lastname@example.org>,
Greg KH <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Subject: Re: A lot of regression reports submitted to bugzilla.kernel.org are apparently ignored, even bisected ones
Date: Wed, 20 Apr 2022 12:32:23 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
On Wed, Apr 20, 2022 at 01:57:12PM +0200, Thorsten Leemhuis wrote:
> > I find such Bugzilla useless - the Components are not matching reality,
> > Products look ok except missing really a lot. Does it have proper
> > assigners based on maintainers? Nope. At least not everywhere.
Nobody has stepped up to maintain bugzilla for the past 10 years. Managing
components, products, assignees -- that's not the job of the infrastructure
team. Linux development is so compartmentalized that cross-subsystem tasks
like bug reporting have been thoroughly neglected.
However, I would argue that bugzilla needs fewer components, not more of them.
Otherwise people get confused and file bugs against "kernel.org" or whatever
happens to be the first entry in the list. For bugzilla to be useful, it needs
to have a bugmaster -- and nobody has volunteered thus far. It's not something
that members of the LF IT team can do, since none of us are kernel developers.
If someone steps up, I'll be happy to grant them admin rights to manage all
the components, etc.
> > All the bug or issue reports I get via email and I think I am not alone
> > in this. All automated tools (kbuild, kernelCI) are using emails for bug
> > reporting. Why having one more system which seems not up to date?
Email is a poor choice when someone needs to share large files (usually,
dumps). Besides, I really don't want stuff like that in public-inbox archives,
This is one major upside of bugzilla -- it can still be largely email-based,
but it also provides a way to share large files without the need to ship them
around as attachments or use some other 3rd-party file sharing services.
> I'm the wrong one to ask, as I think it's a disservice right now that
> needs to be dealt with -- for example by turning it off or by making it
> work properly. But to my knowledge there is nobody really responsible
> for it (apart from Konstantin and his team, but they are afaics only
> responsible for running bugzilla the software -- not for maintaining
> components, products, and such things). That's afaics why we as the
> kernel developers community need to come up with a decision. But maybe
> mailing lists are a bad tool for this and this needs to wait till kernel
> and/or maintainers summit in September (it's already on the list of
> topics I plan to propose).
All that really needs to happen to improve the situation:
1. have an actual kernel developer be responsible for managing bugzilla; this
person would manage components and keep an eye on new bugs to make sure
they get to proper subsystem owners
That's it, there are no other entries here. Bugzilla *can* be a useful tool
and works reasonably well with email back-and-forth, but nobody wants to do
this work -- so everyone ends up blaming the tool.
prev parent reply other threads:[~2022-04-20 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:35 A lot of regression reports submitted to bugzilla.kernel.org are apparently ignored, even bisected ones Thorsten Leemhuis
2022-04-14 7:53 ` Jani Nikula
2022-04-20 12:30 ` Thorsten Leemhuis
2022-04-20 10:31 ` Krzysztof Kozlowski
2022-04-20 11:57 ` Thorsten Leemhuis
2022-04-20 16:32 ` Konstantin Ryabitsev [this message]
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 \
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.