public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Immolo <immoloism@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] A new bugzilla keyword for bug investigation
Date: Fri, 10 Jan 2025 16:34:26 +0000	[thread overview]
Message-ID: <CAHfWF5=dFegtj_m_uOs630Fw0wHotTwvhqhk+6LJnPcrdDWYSA@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_nJ2vOmY=SKfBfwWVZyVUFYeCypn9GkaEzftPjfZdfazg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]

I like this idea, but prefer NEEDS-INVESTIGATION over NEEDS-TRIAGE as the
latter to me is just the state before bugwranglers assign it.

Using https://bugs.gentoo.org/946338 as an example and following on from
Rich's thinking out loud.
I think the person reporting the bug will be one calling for the
NEEDS-INVESTIGATION
as it will be framed in a I found X odd issue, but it's weird I'm the only
one saying it, type of situation.
This would mean we have the fix ready to go but we know we are waiting for
more information from other users before setting on everyone's system
unnecessary.

This is how I see it as bugwrangler though, but NEEDS-INVESTIGATION before
actioning :)

Kind regards,

immolo


On Fri, 10 Jan 2025 at 16:12, Rich Freeman <rich0@gentoo.org> wrote:

> On Fri, Jan 10, 2025 at 3:17 AM Agostino Sarubbo <ago@gentoo.org> wrote:
> >
> > For that reason I would like to propose a new bugzilla KEYWORD, like:
> >
> >
> > - NEEDS-TRIAGE
> >
> > or
> >
> > - NEEDS-INVESTIGATION
>
> Makes a lot of sense, though I'm not sure if it could cause confusion
> for bug wrangling/etc.  I don't think non-prived bugzilla users could
> add the keyword though, so probably no impact there?
>
> The bug wranglers might actually like it for marking stuff that can't
> be assigned easily?  In any case, I'm just thinking out loud about
> whether there is anything in the bug wrangling process that needs
> consideration.
>
> --
> Rich
>
>

[-- Attachment #2: Type: text/html, Size: 2643 bytes --]

  reply	other threads:[~2025-01-10 16:34 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 [this message]
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 ` [gentoo-dev] " Jonas Stein

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='CAHfWF5=dFegtj_m_uOs630Fw0wHotTwvhqhk+6LJnPcrdDWYSA@mail.gmail.com' \
    --to=immoloism@googlemail.com \
    --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