workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: Thorsten Leemhuis <linux@leemhuis.info>,
	workflows@vger.kernel.org, aros@gmx.com,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
	tools@linux.kernel.org
Subject: Re: Introducing bugbot
Date: Wed, 12 Apr 2023 10:07:21 -0400	[thread overview]
Message-ID: <20230412-appear-tiring-f5a896@meerkat> (raw)
In-Reply-To: <87fs958f2a.fsf@kernel.org>

On Wed, Apr 12, 2023 at 03:23:25PM +0300, Kalle Valo wrote:
> > But here I decided to *not* use bugbot, as I know Kalle sometimes is
> > active in bugzilla -- and thus might hate it, if I re-categorize the bug.
> 
> Yeah, for me moving ath11k bugs away from Drivers/network-wireless
> component is not really helpful. And for ath11k I try to look at all
> reported bugs in bugzilla anyway, though just slowly.

Right, I did mean to say that the bot is only limited to Linux/Kernel during
the initial tryout stage. Once I'm more confident that it's not exploding and
mostly doing the right thing, I can enable it for other components.

> While at it, I have some things on my wishlist to make my use of
> bugzilla.kernel.org easier:
> 
> * A new state named UNCONFIRMED and have it as the default state for
>   reported bugs. This would help triaging bugs as some of the reports
>   are not valid. In other words only valid bugs would have NEW state.
>   IIRC the Mozilla project did this back in the day.

This is more hairy than it looks, but I'll try to figure out what happened to
the UNCONFIRMED state in our bugzilla.

> * Use P3 as the default priority for the new bugs. I try to keep ath11k
>   bugs in priority order but new reported bugs having P1 always messes
>   up the list always.

Okay, I set the default to P3, which is nicely in the middle.

-K

  reply	other threads:[~2023-04-12 14:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 21:45 Konstantin Ryabitsev
2023-04-03 21:47 ` Kernel.org Bugbot
2023-04-03 21:51   ` Konstantin Ryabitsev
2023-04-04  5:58 ` Thorsten Leemhuis
2023-04-04  6:57   ` Geert Uytterhoeven
2023-04-04  8:16   ` Bagas Sanjaya
2023-04-04 12:36   ` Konstantin Ryabitsev
2023-04-04 12:55     ` Thorsten Leemhuis
2023-04-04 16:16 ` Artem S. Tashkinov
2023-04-04 17:25   ` Mark Brown
2023-04-04 17:35   ` Konstantin Ryabitsev
2023-04-04 21:39     ` David Sterba
2023-04-08 12:10 ` Thorsten Leemhuis
2023-04-12 12:23   ` Kalle Valo
2023-04-12 14:07     ` Konstantin Ryabitsev [this message]
2023-04-12 16:47       ` Kalle Valo
2023-05-05 15:52 ` Jakub Kicinski
2023-05-05 19:12   ` Konstantin Ryabitsev
2023-05-05 19:32     ` Jakub Kicinski
2023-05-05 19:39       ` Konstantin Ryabitsev
2023-05-05 19:43         ` Jakub Kicinski

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=20230412-appear-tiring-f5a896@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=aros@gmx.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=tools@linux.kernel.org \
    --cc=workflows@vger.kernel.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