[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y1mx6o9k.fsf@kernel.org>
Date: Wed, 12 Apr 2023 19:47:35 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Thorsten Leemhuis <linux@...mhuis.info>, workflows@...r.kernel.org,
aros@....com, linux-kernel@...r.kernel.org,
regressions@...ts.linux.dev, tools@...ux.kernel.org
Subject: Re: Introducing bugbot
Konstantin Ryabitsev <konstantin@...uxfoundation.org> writes:
> On Wed, Apr 12, 2023 at 03:23:25PM +0300, Kalle Valo wrote:
>
>> 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.
I can only imagine how difficult bugzilla can to administer. So if it's
too hairy to get UNCONFIRMED working again don't use too much on it.
This is more like a nice to have feature, not a critical thing.
>> * 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.
Nice, thanks!
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists