From: Olof Johansson <olof@lixom.net>
To: Greg KH <greg@kroah.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Issues with stable process
Date: Thu, 16 Jul 2015 11:14:39 -0700 [thread overview]
Message-ID: <CAOesGMi4RHpEwZ=rFtO+ML74k0ks8hivSBT1pa=OwQqRUB=JDQ@mail.gmail.com> (raw)
In-Reply-To: <20150715160347.GB12543@kroah.com>
On Wed, Jul 15, 2015 at 9:03 AM, Greg KH <greg@kroah.com> wrote:
> On Wed, Jul 15, 2015 at 10:52:13AM -0400, Olof Johansson wrote:
>> On Mon, Jul 13, 2015 at 2:51 PM, Mark Brown <broonie@kernel.org> wrote:
>> > On Mon, Jul 13, 2015 at 02:21:32PM -0400, Steven Rostedt wrote:
>> >
>> >> I disagree. I thought next was a place to have integration of new
>> >> development, and not just a place to test. Really, how many people test
>> >> next compared to Linus's tree? I trip over bugs all the times in
>> >> Linus's tree that's been in -next for almost a whole release cycle.
>> >
>> >> The only bugs that I find that come from -next is integration issues,
>> >> where an interface changes and another subsystem stumbles over it.
>> >> That's exactly what it was for and what it's good at.
>> >
>> > In the embedded space it's much more common to track -next as people are
>> > often working with multiple subsystems so the integration is important.
>> > Most of my code is developed against -next then moved to topic branches
>> > for submission.
>> >
>> > We also catch quite a lot of issues in -next as a result of the work on
>> > boot testing that kernelci.org and Olof's bots are doing, hopefully
>> > that'll start to build out to include test suites like kselftest (I know
>> > there's work in progress there but no ETA as of yet). Things get
>> > exposed to a lot more systems and configurations than individual
>> > maintainers have access to which can shake out issues in code that deals
>> > with hardware.
>>
>> I've stopped running -stable releases through the tester. It didn't
>> fit the way I kept track of what's been built very well and it was
>> hard to capture a useful state in which to test.
>>
>> For a while I tried to capture the current-state-of-the-queue from
>> gregkh's public quilt series ever so often, but it's quite churny.
>> There's an -rc that's posted for review but not tagged and not
>> provided as a git branch of applied patches, so it's hard to
>> automatically test just those.
>>
>> That would be the ideal setup for me though -- tagged or branched -rc
>> candidates of stable releases that I'd be happy to put through the
>> build/boot test at my end.
>
> kernelci now handles -rc stable releases, so would this just be a
> duplication of that work?
Great, then I won't waste my time on it.
-Olof
next prev parent reply other threads:[~2015-07-16 18:14 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-11 16:12 [Ksummit-discuss] [CORE TOPIC] Issues with stable process Sasha Levin
2015-07-12 10:02 ` Geert Uytterhoeven
2015-07-12 13:32 ` Sasha Levin
2015-07-13 0:52 ` NeilBrown
2015-07-13 3:32 ` Andy Lutomirski
2015-07-13 4:27 ` Sasha Levin
2015-07-13 5:10 ` NeilBrown
2015-07-13 22:55 ` Rafael J. Wysocki
2015-07-13 18:21 ` Steven Rostedt
2015-07-13 18:51 ` Mark Brown
2015-07-15 14:52 ` Olof Johansson
2015-07-15 15:59 ` Guenter Roeck
2015-07-15 16:03 ` Greg KH
2015-07-15 16:15 ` Sasha Levin
2015-07-15 16:40 ` Greg KH
2015-07-15 19:34 ` Josh Boyer
2015-07-15 21:21 ` Sasha Levin
2015-07-15 22:34 ` Greg KH
2015-07-15 22:40 ` Sasha Levin
2015-07-16 3:36 ` Greg KH
2015-07-17 0:52 ` Rafael J. Wysocki
2015-07-16 9:06 ` Zefan Li
2015-07-16 18:14 ` Olof Johansson [this message]
2015-07-14 0:42 ` Sasha Levin
2015-07-14 1:02 ` Steven Rostedt
2015-07-14 2:00 ` Sasha Levin
2015-07-14 2:28 ` Jonathan Corbet
2015-07-14 3:48 ` Stephen Rothwell
2015-07-14 7:14 ` Geert Uytterhoeven
2015-07-14 11:03 ` James Bottomley
2015-07-14 13:29 ` Steven Rostedt
2015-07-14 20:17 ` James Bottomley
2015-07-14 20:45 ` Mark Brown
2015-07-14 22:12 ` Steven Rostedt
2015-07-14 22:36 ` Andy Lutomirski
2015-09-01 8:44 ` Jani Nikula
2015-09-01 20:52 ` Greg KH
2015-09-01 21:00 ` Sasha Levin
2015-09-01 21:08 ` Jiri Kosina
2015-09-01 22:47 ` Sasha Levin
2015-09-02 10:10 ` Luis Henriques
2015-07-16 0:53 ` Rafael J. Wysocki
2015-07-16 11:50 ` Mark Brown
2015-07-14 3:42 ` Stephen Rothwell
2015-07-14 7:03 ` Geert Uytterhoeven
2015-07-14 10:46 ` Mark Brown
2015-07-14 13:57 ` Sasha Levin
2015-07-14 15:25 ` Mark Brown
2015-07-14 15:32 ` Sasha Levin
2015-07-14 15:38 ` Steven Rostedt
2015-07-14 15:53 ` Sasha Levin
2015-07-14 16:02 ` Steven Rostedt
2015-07-14 19:30 ` Sasha Levin
2015-07-14 19:38 ` Steven Rostedt
2015-07-15 1:49 ` NeilBrown
2015-07-15 2:09 ` Sasha Levin
2015-07-15 2:28 ` NeilBrown
2015-07-15 10:13 ` James Bottomley
2015-07-15 23:24 ` NeilBrown
2015-07-16 1:05 ` Andy Lutomirski
2015-07-16 1:43 ` Linus Torvalds
2015-07-16 1:25 ` Steven Rostedt
2015-07-16 9:19 ` James Bottomley
2015-07-16 12:33 ` Jonathan Cameron
2015-08-03 8:32 ` Fengguang Wu
2015-07-14 15:56 ` Mark Brown
2015-07-14 19:01 ` Sasha Levin
2015-07-14 19:18 ` Geert Uytterhoeven
2015-07-14 19:31 ` Sasha Levin
2015-07-15 9:26 ` Jan Kara
2015-07-16 12:53 ` Mark Brown
2015-07-13 9:22 ` Jan Kara
2015-07-13 20:51 ` Greg KH
2015-07-14 0:51 ` Sasha Levin
2015-07-14 2:46 ` NeilBrown
2015-07-15 19:41 ` Steven Rostedt
2015-07-15 20:14 ` James Bottomley
2015-07-12 15:01 ` Masami Hiramatsu
2015-07-13 10:15 ` Zefan Li
2015-07-13 16:12 ` Sasha Levin
2015-07-14 10:08 ` Zefan Li
2015-07-14 14:00 ` Sasha Levin
2015-07-15 0:01 ` Greg Kroah-Hartman
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='CAOesGMi4RHpEwZ=rFtO+ML74k0ks8hivSBT1pa=OwQqRUB=JDQ@mail.gmail.com' \
--to=olof@lixom.net \
--cc=greg@kroah.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=sasha.levin@oracle.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.