From: Hussam Al-Tayeb <ht990332@gmx.com>
To: Sasha Levin <sashal@kernel.org>,
Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Cc: stable@vger.kernel.org
Subject: Re: Suggestion: Lengthen the review period for stable releases from 48 hours to 7 days.
Date: Wed, 18 Nov 2020 20:02:16 +0200 [thread overview]
Message-ID: <b50f0ee318cbedcd9bca95a1af00b520c4b3126b.camel@gmx.com> (raw)
In-Reply-To: <20201118140953.GC629656@sasha-vm>
On Wed, 2020-11-18 at 09:09 -0500, Sasha Levin wrote:
> On Tue, Nov 17, 2020 at 11:29:16PM +0100, Christoph Biedl wrote:
> > On the other hand the pace of the stable patches became fairly
> > high¹, so
> > during a week of -rc review a *lot* of them will queue up and I
> > predict
> > we'll see requests for fast-laning some of them. Also, a release
> > would
> > immediately be followed by the next -rc review period, a procedure
> > that
> > gives me a bad feeling.
>
> Keep in mind that the stable tree derives itself from Linus's tree -
> it's not a development tree on it's own and we don't control how many
> fixes flow into Linus's tree (and as a result into the stable tree).
>
> This means that it doesn't matter how long the review window is open
> for, you'll be getting the same time to review a single patch -
> whether
> we do 200 patches twice a week or 400 patches once a week. We can't
> create time by moving review windows around.
>
How long does it take for patches reaching Linux's tree to propagate
down to the stable trees and is there is mechanism for identifying
followup patches?
For instance, patch A fixes bug X but we eventually find out that this
patch did not fix all occurrences of the bug or caused a regression and
hence the author immediately sent patch B for inclusion in mainline
(Linux's tree).
Is patch B automatically identified for inclusion in stable as well?
In short, is there a guarantee that stable trees are as stable or
better than mainline through the current SOP?
Regards,
Hussam.
next prev parent reply other threads:[~2020-11-18 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 15:40 Suggestion: Lengthen the review period for stable releases from 48 hours to 7 days Hussam Al-Tayeb
2020-11-14 19:16 ` Hussam Al-Tayeb
2020-11-17 8:01 ` Pavel Machek
2020-11-17 20:53 ` Hussam Al-Tayeb
2020-11-17 22:29 ` Christoph Biedl
2020-11-18 7:20 ` Greg KH
2020-11-18 14:09 ` Sasha Levin
2020-11-18 18:02 ` Hussam Al-Tayeb [this message]
2020-11-18 18:12 ` Greg KH
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=b50f0ee318cbedcd9bca95a1af00b520c4b3126b.camel@gmx.com \
--to=ht990332@gmx.com \
--cc=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 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.