From: Sasha Levin <sashal@kernel.org>
To: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
Cc: Hussam Al-Tayeb <ht990332@gmx.com>, 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 09:09:53 -0500 [thread overview]
Message-ID: <20201118140953.GC629656@sasha-vm> (raw)
In-Reply-To: <1605651898@msgid.manchmal.in-ulm.de>
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.
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-11-18 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17c526d0c5f8ed8584f7bee9afe1b73753d1c70b.camel@gmx.com>
[not found] ` <20201117080141.GA6275@amd>
2020-11-17 20:53 ` Suggestion: Lengthen the review period for stable releases from 48 hours to 7 days Hussam Al-Tayeb
2020-11-17 22:29 ` Christoph Biedl
2020-11-18 7:20 ` Greg KH
2020-11-18 14:09 ` Sasha Levin [this message]
2020-11-18 18:02 ` Hussam Al-Tayeb
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=20201118140953.GC629656@sasha-vm \
--to=sashal@kernel.org \
--cc=ht990332@gmx.com \
--cc=linux-kernel.bfrz@manchmal.in-ulm.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox