linux-kernel - Re: [PATCH 4.19 000/243] 4.19.89-stable review

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20191213140902.GA2436279@kroah.com>
Date:   Fri, 13 Dec 2019 15:09:02 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Pavel Machek <pavel@...x.de>, linux-kernel@...r.kernel.org,
        torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        shuah@...nel.org, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 4.19 000/243] 4.19.89-stable review

On Fri, Dec 13, 2019 at 05:56:41AM -0800, Guenter Roeck wrote:
> On 12/13/19 1:30 AM, Pavel Machek wrote:
> > Hi!
> > 
> > > This is the start of the stable review cycle for the 4.19.89 release.
> > > There are 243 patches in this series, all will be posted as a response
> > > to this one.  If anyone has any issues with these being applied, please
> > > let me know.
> > > 
> > > Responses should be made by Fri, 13 Dec 2019 14:56:06 +0000.
> > > Anything received after that time might be too late.
> > 
> > Is there something funny going on with the timing, again? I see that
> > 4.19.89 is already out:
> > 
> 
> Just for the record, in my opinion it is perfectly fine to publish stable
> releases early after all expected feedback is in. That lets me merge the
> release early today and gives me time to fix any merge related problems.
> I don't see the benefit of waiting until 14:46:07.

And that's exactly what I do.  I wait for the expected feedback to come
in and if it looks good, I do a release.

I ususally delay the "official" announcement a bit to give the Android
builder/testers some time to give feedback after I make the tarballs as
they are good at finding problems no one else seems to catch, and then I
do the email announcements.

thanks,

greg k-h