#meeting:fedoraproject.org: F40 Beta Go/No-Go-meeting

Meeting started by @amoloney:fedora.im at 17:01:54 UTC

INFO: roll call (@amoloney:fedora.im, 17:02:45)
INFO: purpose of this meeting (@amoloney:fedora.im, 17:08:46)
INFO: Purpose of this meeting is to check whether or not F40 Beta is ready for shipment, according to the release criteria. (@amoloney:fedora.im, 17:09:07)
INFO: this is determined in a few ways (@amoloney:fedora.im, 17:09:30)
INFO: Release candidate compose is available (@amoloney:fedora.im, 17:10:17)
INFO: No remaining blocker bugs (@amoloney:fedora.im, 17:10:35)
INFO: Test matrices are complete (@amoloney:fedora.im, 17:10:41)
INFO: Fedora CoreOS and IoT are ready (@amoloney:fedora.im, 17:10:59)
INFO: Current Status: RC (@amoloney:fedora.im, 17:11:09)
INFO: we do have an RC for F40 Beta, moving on to Blocker Status (@amoloney:fedora.im, 17:15:46)
INFO: Blockers (@amoloney:fedora.im, 17:15:59)
INFO: link https://qa.fedoraproject.org/blockerbugs/milestone/40/beta/buglist (@amoloney:fedora.im, 17:16:30)
TOPIC:(2269407) Fedora minimal does not boot on Raspberry Pi 4b+ (@adamwill:fedora.im, 17:20:33)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2269407 (@adamwill:fedora.im, 17:20:37)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1522 (@adamwill:fedora.im, 17:20:41)
INFO: Proposed Blocker, bcm283x-firmware, NEW (@adamwill:fedora.im, 17:20:43)
AGREED: 2269407 - AcceptedBlocker (Beta) - this is accepted as a violation of "Release-blocking ARM disk images must boot to the initial-setup utility" on the Pi 4b+. Minimal is a release-blocking image, and Pi 4s are release-blocking ARM devices (@adamwill:fedora.im, 17:32:11)

TOPIC:(2269373) Fedora Media Writer (Windows Version) writes images that fail the checksum check on boot (@adamwill:fedora.im, 17:32:30)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2269373 (@adamwill:fedora.im, 17:32:33)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1520 (@adamwill:fedora.im, 17:32:37)
INFO: Proposed Blocker, mediawriter, NEW (@adamwill:fedora.im, 17:32:40)
INFO: Ticket vote: BetaBlocker (+0,0,-3) (-geraldosimiao, -kparal, -sgallagh) (@adamwill:fedora.im, 17:32:43)
AGREED: 2269373 - RejectedBlocker (Beta) - this is rejected as not violating any release criteria (@adamwill:fedora.im, 17:35:27)
INFO: other outstanding, unaddressed blockers: (@adamwill:fedora.im, 17:36:13)
INFO: (2267968) Raspberry Pi 400 shows nothing on screen when booting Fedora 40 images (even before grub) (@adamwill:fedora.im, 17:36:34)
LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2267968 (@adamwill:fedora.im, 17:36:38)
INFO: (2269385) rhgb breaks custom/minimal install on most filesystem layouts (@adamwill:fedora.im, 17:36:48)
LINK: !link https://bugzilla.redhat.com/show_bug.cgi?id=2269385 (@adamwill:fedora.im, 17:36:52)
INFO: (2113005) Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to boot on some boards (@adamwill:fedora.im, 17:37:00)
LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2113005 (@adamwill:fedora.im, 17:37:06)
INFO: (2259264) Fedora fails to boot via BOOT/bootaa64->fbaa64 on UEFI machines with EFI_MEMORY_ATTRIBUTES_PROTOCOL (@adamwill:fedora.im, 17:37:18)
LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2259264 (@adamwill:fedora.im, 17:37:21)

AGREED: The Fedora Linux 40 Beta is NO-GO (@amoloney:fedora.im, 17:50:22)
INFO: The next F40 Beta Go/No-Go meeting will be on Thursday 21st March @ 1700 UTC (@amoloney:fedora.im, 17:50:59)
INFO: F40 Beta will now shift to target date #2: Tuesday 2024-03-26 (@amoloney:fedora.im, 17:51:34)
ACTION: amoloney to announce decision and adjust schedule (@amoloney:fedora.im, 17:52:05)

IDEA: #proposed: try to do a retrospective of the F40 release (@amoloney:fedora.im, 18:02:31)

Meeting ended at 18:17:11 UTC