From: Jonas Stein <jstein@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] A new bugzilla keyword for bug investigation
Date: Sat, 18 Jan 2025 20:55:13 +0100 [thread overview]
Message-ID: <fb7f8e21-ec98-4aec-a589-9fecbe6a889d@gentoo.org> (raw)
In-Reply-To: <2645278.Lt9SDvczpP@fcf>
> For that reason I would like to propose a new bugzilla KEYWORD, like:
>
> - NEEDS-TRIAGE
> or
> - NEEDS-INVESTIGATION
>
> or whatever you think is better.
>
> With that KEYWORD we can set-up a saved search and 'experienced' devs can help to
> diagnose the issue.
>
> This KEYWORD is supposed to be set manually and not supposed to be set automatically
> when there is a missing "error: " string. And obviously it can be used by everyone that
> needs help.
>
> Before send this to the mailing list, I talked about that with sam (since he is one of those
> who does this activity) and agreed.
>
> What do you think?
In general I think it is a good idea. The difficulty is to find a good
tag that is not misunderstood.
It should not be mixed with
"there are error messages and a user forgot to attach the log"
I am also undecided how useful this would be if a bot creates now tons
of "NEED_INVESTIGATION" bugs if we have no bots fixing these. :-)
A NEED_INVESTIGATION bug will take 100 times of the ressources compared
to a usual bug.
--
Best,
Jonas
prev parent reply other threads:[~2025-01-18 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 8:17 [gentoo-dev] A new bugzilla keyword for bug investigation Agostino Sarubbo
2025-01-10 16:03 ` Jaco Kroon
2025-01-10 16:12 ` Rich Freeman
2025-01-10 16:34 ` Immolo
2025-01-11 6:53 ` Agostino Sarubbo
2025-01-18 18:02 ` Sam James
2025-01-19 17:19 ` [gentoo-dev] " Duncan
2025-01-18 19:55 ` Jonas Stein [this message]
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=fb7f8e21-ec98-4aec-a589-9fecbe6a889d@gentoo.org \
--to=jstein@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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