From: Guenter Roeck <linux@roeck-us.net>
To: Theodore Ts'o <tytso@mit.edu>, Olof Johansson <olof@lixom.net>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] Kernel Summit Agenda -- 2nd draft
Date: Wed, 21 Oct 2015 08:20:54 -0700 [thread overview]
Message-ID: <5627AD56.7050500@roeck-us.net> (raw)
In-Reply-To: <20151021145626.GD2165@thunk.org>
On 10/21/2015 07:56 AM, Theodore Ts'o wrote:
> On Tue, Oct 20, 2015 at 07:36:31PM -0700, Olof Johansson wrote:
>>> 3:30 - Kernel Development Process (Is Linus happy?)
>>
>> We usually check in with Stephen Rothwell as well to see how happy or
>> miserable he is, probably in the same slot though?
>
> Yep. Given the recent "commits in -rc1 not in next" statistic have
> been consistently getting better for the last 3 or 4 releases, I'm
> assuming/hoping this means that on the whole both Linus and Stephen
> are probably pretty happy with how things are going on the development
> process front.
>
> But if Linus, Stephen, or anyone else for that matter has thoughts or
> suggestions about how we can do things better, this is the slot for
> it.
>
Mainline is getting pretty good. Build and runtime failures introduced
in commit windows tend to get fixed around rc3-ish (as measured with
"my builds and qemu tests all pass"), which is much better than it used to be.
Number of build and runtime breakages in -next is a bit high, and fixes are
sometimes slow to roll in. At least in part this is because those responsible
for breakages are not informed, but I have also seen problems which were
known for weeks to propagate into mainline before they got fixed, even if
the culprit was informed. This could use some improvement, though I am not
really sure how we could get there. Make more noise ?
Guenter
next prev parent reply other threads:[~2015-10-21 15:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 22:03 [Ksummit-discuss] Kernel Summit Agenda -- 2nd draft Theodore Ts'o
2015-10-20 23:17 ` Jason Cooper
2015-10-21 2:36 ` Olof Johansson
2015-10-21 14:56 ` Theodore Ts'o
2015-10-21 15:20 ` Guenter Roeck [this message]
2015-10-21 16:09 ` Mark Brown
2015-10-21 16:37 ` Guenter Roeck
2015-10-21 17:24 ` Luck, Tony
2015-10-21 18:53 ` Jonathan Corbet
2015-10-21 17:25 ` Mark Brown
2015-10-22 15:25 ` Theodore Ts'o
2015-10-22 20:01 ` Alexandre Belloni
2015-10-24 15:19 ` Rafael J. Wysocki
2015-10-26 5:56 ` Luis R. Rodriguez
2015-10-26 6:12 ` Eric W. Biederman
2015-10-26 6:28 ` Josh Triplett
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=5627AD56.7050500@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ksummit-discuss@lists.linux-foundation.org \
--cc=olof@lixom.net \
--cc=tytso@mit.edu \
/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.