Meeting started by @amoloney:fedora.im at 17:01:54 UTC
Meeting summary
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)
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)