public inbox for patches@lists.linux.dev
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Peter Schneider <pschneider1968@googlemail.com>
Cc: Mark Brown <broonie@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	patches@lists.linux.dev, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.19 000/844] 6.19.6-rc1 review
Date: Sun, 1 Mar 2026 11:11:12 -0500	[thread overview]
Message-ID: <aaRlIJFcOpBVlD9f@laps> (raw)
In-Reply-To: <055deed0-4b00-422e-8afb-5c3e577a6046@googlemail.com>

On Sun, Mar 01, 2026 at 04:15:04PM +0100, Peter Schneider wrote:
>Am 01.03.2026 um 13:05 schrieb Mark Brown:
>[...]
>>I've previously noted that releasing -rcs on a Friday afternoon isn't
>>good for ensuring coverage (this was what happened with 6.19.2 and
>>related releases...), the same is also true for releasing them on a
>>Saturday with a deadline that's very early on Monday for a lot of the
>>world.
>
>I second that, and would like to suggest that when a stable RC release 
>is done on a Friday afternoon or even on a Saturday, it would be 
>better to extend the response deadline until Tuesday afternoon, so 
>that people who want to help with testing have a chance to do so 
>without having to "sacrifice" weekend/family time.

As far as the -rc goes, we just release it whenever our queues get longer. I
don't think that that matters if that goes out on a Friday.

For the release deadline, you definitely shouldn't sacrifice personal time to
test: at the end of the day, releasing is a judgement call, and if we don't see
the usual reports then we will hold off the release for a bit until we know
what is going on.

-- 
Thanks,
Sasha

  reply	other threads:[~2026-03-01 16:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 17:18 [PATCH 6.19 000/844] 6.19.6-rc1 review Sasha Levin
2026-02-28 18:12 ` Ronald Warsow
2026-02-28 22:13   ` Woody Suwalski
2026-02-28 23:41     ` Barry K. Nathan
2026-03-01  0:33     ` Peter Schneider
2026-03-01  1:17     ` Sasha Levin
2026-03-01  2:46 ` Peter Schneider
2026-03-01  8:36 ` Takeshi Ogasawara
2026-03-01  8:49 ` Barry K. Nathan
2026-03-01 16:43   ` Barry K. Nathan
2026-03-02  0:49     ` Sasha Levin
2026-03-02  6:34       ` Barry K. Nathan
2026-03-01  8:54 ` Brett A C Sheffield
2026-03-01 12:05 ` Mark Brown
2026-03-01 15:15   ` Peter Schneider
2026-03-01 16:11     ` Sasha Levin [this message]
2026-03-01 16:20       ` Mark Brown
2026-03-01 21:49 ` Ron Economos
2026-03-01 23:48 ` Miguel Ojeda
2026-03-02  0:53 ` Hardik Garg
2026-03-02 13:13 ` Jon Hunter

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=aaRlIJFcOpBVlD9f@laps \
    --to=sashal@kernel.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=pschneider1968@googlemail.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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