All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Laura Abbott <labbott@redhat.com>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs!
Date: Wed, 5 Jun 2019 08:49:40 -0400	[thread overview]
Message-ID: <20190605124940.GC29739@sasha-vm> (raw)
In-Reply-To: <f8b164b6-475d-99e8-1720-965d06ddc392@redhat.com>

On Tue, Jun 04, 2019 at 02:09:19PM -0400, Laura Abbott wrote:
>On 6/3/19 5:10 PM, Sasha Levin wrote:
>>Maybe we could sync up our bugtrackers with the kernel's release cycle?
>>close all bugs older than a certain kernel version once the
>>corresponding stable kernel goes EoL?
>
>We do something like this for Fedora. After the new kernel gets rebased,
>we ask the reporters if the bug is still reproducible. This helps
>prune down some of the one off cases nobody ever saw again as well as
>issues which were actually fixed. Humans sometimes get annoyed at this as
>it looks like we're not paying attention but bots wouldn't care if we
>closed their own issues.

Sadly that's reality, we can't fix *all* bugs, so sometimes real bugs
would get closed but then hopefully be re-opened again if bots/users are
still hitting them.

Maybe they should be closed with a "-ENOREPRO" which would hopefully
encourage those users/bots to try and repro the issue on a newer version
of the kernel.

--
Thanks,
Sasha

  reply	other threads:[~2019-06-05 12:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 23:30 [Ksummit-discuss] [MAINTAINERS SUMMIT] Squashing bugs! 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
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 [this message]
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=20190605124940.GC29739@sasha-vm \
    --to=sashal@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=labbott@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.