ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	Laura Abbott <labbott@redhat.com>,
	ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Mon, 3 Jun 2019 13:48:22 -0700	[thread overview]
Message-ID: <CAHk-=wgVYafLVe-ggAyWdC4Fxg7fCvJP5vgkLJSWPQhk_Xi-Cw@mail.gmail.com> (raw)
In-Reply-To: <20190603180953.GA17954@chatter.i7.local>

On Mon, Jun 3, 2019 at 11:10 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> May I recommend using a project like git-bug [1] instead of a mailing
> list?

I'm not a huge fan of mailing lists only for bug handling, but on the
other hand, I do think that a bug handling thing fundamentally needs

 (a) automatic aging out of bug reports

 (b) targeted push notifications (ie ractically speaking - email)

and that the email part is important. And it can't just be a "hey,
something changed". It needs to contain enough information in the
email to give a developer sufficient knowledge that the developer
knows whether it's even worth it looking deeper at the bug, and
looking at the database (in fact, it should contain enough actual
information that for simple issues, the developer should go "D'oh!"
and just fix the bug).

We went through this with syzbot already, where the notification was
too heavy-handed and not useful. It has improved immensely. There's a
back-end with lots more data, but the emails have gone from "illegible
data" to "pretty informational", and I think it improved peoples
reaction to them a lot.

Apparently syzbot doesn't do well on the (a) side though. Honestly,
any system that just keeps things open for 300+ days has something
wrong with it. At some point it needs to be automatically either
closed, or re-notified. The "just keep it around" is simply not an
option.

                  Linus

  parent reply	other threads:[~2019-06-03 20:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 23:30 Shuah Khan
2019-05-31 12:01 ` Laura Abbott
2019-05-31 15:56   ` Shuah Khan
2019-06-03  5:01     ` Leon Romanovsky
2019-05-31 22:15   ` Kees Cook
2019-06-03 10:42     ` Jan Kara
2019-06-04 18:29       ` Laura Abbott
2019-06-03 16:48     ` Shuah Khan
2019-06-02 18:09   ` Sasha Levin
2019-06-03 17:25     ` Shuah Khan
2019-06-03 18:09       ` Konstantin Ryabitsev
2019-06-03 19:32         ` Shuah Khan
2019-06-03 20:48         ` Linus Torvalds [this message]
2019-06-03 21:10           ` Sasha Levin
2019-06-03 21:15             ` Jiri Kosina
2019-06-03 21:23               ` Linus Torvalds
2019-06-03 21:28                 ` Jiri Kosina
2019-06-03 22:11             ` Mark Brown
2019-06-04 17:16               ` Shuah Khan
2019-06-05  9:27                 ` Mark Brown
2019-06-05 11:48                   ` Geert Uytterhoeven
2019-06-05 18:16                     ` Shuah Khan
2019-06-05 13:19                 ` Sasha Levin
2019-06-05 19:05                   ` Shuah Khan
2019-06-04 18:09             ` Laura Abbott
2019-06-05 12:49               ` Sasha Levin
2019-06-04 21:43           ` Konstantin Ryabitsev
2019-06-04 22:02             ` Shuah Khan
2019-06-04 22:22               ` Konstantin Ryabitsev
2019-06-05 17:54                 ` Shuah Khan
2019-06-03 20:59       ` Sasha Levin
  -- strict thread matches above, loose matches on Subject: below --
2019-05-29 22:34 Shuah Khan

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='CAHk-=wgVYafLVe-ggAyWdC4Fxg7fCvJP5vgkLJSWPQhk_Xi-Cw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=labbott@redhat.com \
    --cc=sashal@kernel.org \
    --cc=skhan@linuxfoundation.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