From: Laura Abbott <labbott@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Bug reporting feedback loop
Date: Sun, 25 Jun 2017 10:11:19 -0700 [thread overview]
Message-ID: <af2f71f7-27bf-6165-c6fb-e90b3bb23e6a@redhat.com> (raw)
In-Reply-To: <20170623145229.GB1855@kroah.com>
On 06/23/2017 07:52 AM, Greg KH wrote:
> On Wed, Jun 21, 2017 at 03:34:11PM -0700, Laura Abbott wrote:
>> - There's still a gap between when bugs hit Linus' tree and when
>> stable releases come out. This is not a knock against stable or
>> a request for stable to go faster :). I try
>> and monitor stable@ for fixes but there still seems to be a
>> large time gap for identifying fixes that have been fixes in
>> master that are relevant to a recent stable release.
>
> Ok, I'll bite, what exactly do you mean by "large time"? During the
> -rc1 merge window, it can take a few weeks for me to catch up with the
> large onslaught of patches marked for stable, but almost all of those
> were determined by the develoers to not be all-so-serious, as they were
> delayed in getting to Linus for -rc1, and not before.>
'large' is my completely biased perception :)
Fedora generally does not rebase until the .2 or .3 stable release
which usually takes care of most of the -rc1 issue. The problem
tends to come from issues which are not found until later -rcs
and for whatever reason haven't made it to stable yet.
> You can always email and ask for specific patches to be queued up now,
> as I go through the list in a semi-random manner.
>
If I can find the patch, I have no problem bringing it into Fedora
or requesting it for stable. Finding a patch is the tricky part
which I'd like to improve. My current technique relies on a combination
of good guessing where a fix might come from and random inspiration.
Maybe this is just the curse of the maintainer and there isn't a
better method but having something a bit more systematic to check
would be useful, especially for training other maintainers.
> After the big -rc1 chunk of patches are merged, it's usually only a week
> at most before the patches hit a stable release, people usually complain
> it goes too fast, not that it's too slow these days.
> > thanks,
>
> greg k-h
>
Thanks,
Laura
prev parent reply other threads:[~2017-06-25 17:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 22:34 Laura Abbott
2017-06-22 12:36 ` Jiri Kosina
2017-06-27 17:53 ` Luis R. Rodriguez
2017-06-27 18:26 ` Laurent Pinchart
2017-06-27 18:30 ` James Bottomley
2017-06-27 18:41 ` Daniel Vetter
2017-06-27 19:02 ` Luis R. Rodriguez
2017-06-27 19:46 ` Guenter Roeck
2017-06-28 10:19 ` Mark Brown
2017-06-27 22:35 ` Jiri Kosina
2017-06-28 6:59 ` Takashi Iwai
2017-06-27 18:31 ` Takashi Iwai
2017-06-27 19:04 ` Luis R. Rodriguez
2017-06-28 8:04 ` Daniel Vetter
2017-06-22 14:08 ` Takashi Iwai
2017-06-22 14:12 ` Jiri Kosina
2017-06-22 14:24 ` Takashi Iwai
2017-06-28 13:12 ` Jani Nikula
2017-06-28 13:13 ` Takashi Iwai
2017-06-22 15:34 ` James Bottomley
2017-06-23 14:52 ` Greg KH
2017-06-23 20:28 ` Jiri Kosina
2017-06-25 17:11 ` Laura Abbott [this message]
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=af2f71f7-27bf-6165-c6fb-e90b3bb23e6a@redhat.com \
--to=labbott@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.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