[Ksummit-discuss] [CORE TOPIC] Issues with stable process
Andy Lutomirski
luto at amacapital.net
Mon Jul 13 03:32:23 UTC 2015
On Sun, Jul 12, 2015 at 5:52 PM, NeilBrown <neilb at suse.com> wrote:
>
> I've been bitten by this a couple of times too. At least two fairly
> serious md bugs *never* got into a release from Linus, but did get into
> -stable and at least one into a vendor kernel.
>
I've had -stable regression issues, too (both regressions I caused and
regressions I've been bitten by).
>
> I would rather that the default was that patches don't go into -stable
> until they have
> - been in a full release from Linus and
> - been in a Linus's tree for at least 2 weeks.
> (or 1 week times the age of the target in releases.
> So a fix in 4.4 get to 4.3-stable after a week, 4.2-stable
> after 2 weeks etc .... maybe I'm going over-board here).
>
> Many fixes are important but simply aren't that urgent so the two or
> more weeks is no great cost.
I tend to agree. It makes me quite nervous when brand-new
non-critical fixes get backported before they've had a nice soak in
some -rc releases.
--Andy
More information about the Ksummit-discuss
mailing list