[Ksummit-discuss] [CORE TOPIC] stable workflow

[Jani Nikula]

On Sun, 10 Jul 2016, James Bottomley <James.Bottomley at HansenPartnership.com> wrote:
> If I'm suspicious of something, I usually mark it not to be backported
> until we've got some testing:
>
> cc: stable at vger.kernel.org # delay until 4.8-rc1
>
> Greg seems to be able to cope with this.

So what do you do to prevent said commit from being backported to stable
kernels if it turns out bad (at any step of the way, really)? How does
it work? cc: stable is fire-and-forget, but sadly without self-destruct
when things go bad.

And where do you set the paranoia level with that "delay until" thing?

Generally adding cc: stable is like, this is clearly a fix to a bug that
is present in stable kernels, and the bug should be fixed, but I have no
idea nor resources to review or test if this is the right fix across all
stable kernels. You end up relying on your gut feeling too much to be
comfortable. You have to make the call too early in the process.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Technology Center