Date: Tue, 25 Jun 2024 11:18:05 -0700 From: Gleb Smirnoff <glebius@freebsd.org> To: freebsd-current@freebsd.org, src-committers@freebsd.org Subject: Re: June 2024 stabilization week Message-ID: <ZnsJ3f_H569E_h02@cell.glebi.us> In-Reply-To: <ZnknhTrRzUVhbxBH@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
On Mon, Jun 24, 2024 at 01:00:05AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the June 2024 stabilization week T> started with FreeBSD/main at main-n270917-5dbf886104b4, which was tagged as T> main-stabweek-2024-Jun. The 5dbf886104b4 aka main-stabweek-2024-Jun passed regression A/B testing at Netflix with no issues. I also updated my desktops (using nVidia graphics) and home router to that revision, also no issues noticed. We have had a regression in the previous stabilization cycle, which went unnoticed back then - the tpm(4) driver failed to attach on ACPI bus. The problem already fixed in main, but not in main-stabweek-2024-Jun! Given that TPM is still not a ubiquitous thing around, I decided not to create a branch just to cherry pick that. If using TPM you can either update all the way to bbecd3148abf or cherry-pick that revision on top of main-stabweek-2024-Jun. Unless we receive any regression report in this email thread until Wednesday morning at 8:00 UTC, let's declare the stabilization cycle done by that time. Thanks everyone! -- Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZnsJ3f_H569E_h02>