mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hussam Al-Tayeb <ht990332@gmx.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion: Lengthen the review period for stable releases from 48 hours to 7 days.
Date: Sat, 14 Nov 2020 21:16:33 +0200	[thread overview]
Message-ID: <5be77264b98c271668935e4b6ff0d8d558e8298b.camel@gmx.com> (raw)
In-Reply-To: <17c526d0c5f8ed8584f7bee9afe1b73753d1c70b.camel@gmx.com>

On Sat, 2020-11-14 at 17:40 +0200, Hussam Al-Tayeb wrote:
> Hello. I would like to suggest lengthening the review period for
> stable
> releases from 48 hours to 7 days.
> The rationale is that 48 hours is not enough for people to test those
> stable releases and make sure there are no regressions for particular
> workflows.
> This is especially important for companies deploying those kernels in
> production machines. Often those releases are on weekends as well
> further limiting the ability to test.
> It is of course possible to skip stable updates that have large
> numbers
> of patches and only update once a month but I feel a longer testing
> period will work best for everyone.
> It is, of course, always possible to exempt urgent security releases
> from the waiting period.
>
> Thank you.
> Hussam.
>

One more note. This is not a random internet rant. I actually do need
more than 48 hours to test new stable kernels and I believe others do
too.
Regards,
Hussam.


  reply	other threads:[~2020-11-14 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 15:40 Hussam Al-Tayeb
2020-11-14 19:16 ` Hussam Al-Tayeb [this message]
2020-11-17  8:01 ` Pavel Machek

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=5be77264b98c271668935e4b6ff0d8d558e8298b.camel@gmx.com \
    --to=ht990332@gmx.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®