workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Artem S. Tashkinov" <aros@gmx.com>,
	workflows@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Introducing bugbot
Date: Tue, 4 Apr 2023 23:39:17 +0200	[thread overview]
Message-ID: <20230404213917.GG19619@twin.jikos.cz> (raw)
In-Reply-To: <20230404-uncrown-detonate-8bc1ac@meerkat>

On Tue, Apr 04, 2023 at 01:35:34PM -0400, Konstantin Ryabitsev wrote:
> On Tue, Apr 04, 2023 at 04:16:08PM +0000, Artem S. Tashkinov wrote:
> > I love everything about what you've done except I've got a minor feature
> > request for the kernel bugzilla and this new workflow specifically.
> 
> Great to hear.
> 
> > Let's have a bot which polls open bug reports every 3-6 months with this
> > question:
> > 
> > "Is this still an issue in the current kernel? Please leave a comment or
> > this bug report will be closed due to inactivity".
> 
> I plan to do it slightly differently -- there will be a "housekeeping" command
> running daily that will auto-close bugs that haven't seen any activity for a
> defined period (90 days, for example), with a message like:
> 
> "This bug is now closed due to inactivity. Please reopen if this issue is
> still relevant with the latest kernel version."

Will there be a way to opt out of this? I'd rather see any bug closed
after an inspection from a human, I find the auto-close messages a bit
rude and I've read similar sentiment from others. The upstream bugzilla
is a best-effort level of support so it's true that bugs are left open
for months, sometimes years unfortunately, but I've seen many cases where
the report is valid or the "fix" is to improve documentation.

If we had enough people routinely going through the reports then some
sort of reminders would make sense but we don't. I take the bug
reports a task pool if there aren't more pressing things to do, which
may not be the same way how others use bugzilla.k.org so I'd be fine
with opting out of the auto-close or maybe out of any bugbot
interactions.

  reply	other threads:[~2023-04-04 21:39 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 [this message]
2023-04-08 12:10 ` Thorsten Leemhuis
2023-04-12 12:23   ` Kalle Valo
2023-04-12 14:07     ` Konstantin Ryabitsev
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=20230404213917.GG19619@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=aros@gmx.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.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