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

Meeting started by @amoloney:fedora.im at 17:00:51 UTC

INFO: Purpose of this meeting is to check whether or not F40 Final is ready for shipment, according to the release criteria. (@amoloney:fedora.im, 17:02:38)
INFO: This is determined in a few ways: (@amoloney:fedora.im, 17:02:52)
INFO: 1. Release candidate compose is available (@amoloney:fedora.im, 17:03:02)
INFO: 2. No remaining blocker bugs (@amoloney:fedora.im, 17:03:12)
INFO: 3. Test matrices are fully completed (@amoloney:fedora.im, 17:03:22)
INFO: 4. Fedora CoreOS and IoT are ready (@amoloney:fedora.im, 17:03:33)

INFO: the RC 1.13 https://dl.fedoraproject.org/pub/alt/stage/40_RC-1.13/ is what we will be deciding release readiness for Fedora Linux 40 final at the go/no-go meeting (@amoloney:fedora.im, 17:06:51)

LINK: https://qa.fedoraproject.org/blockerbugs/milestone/40/final/buglist (@amoloney:fedora.im, 17:08:47)

TOPIC:(2274006) Unable to Boot - efibootmgr failed with "Could not prepare Boot variable: Invalid argument", CreateBLSEntriesTask task did not run, thus no bootloader entry (@adamwill:fedora.im, 17:09:31)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274006 (@adamwill:fedora.im, 17:09:37)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1575 (@adamwill:fedora.im, 17:09:40)
INFO: Proposed Blocker, efibootmgr, NEW (@adamwill:fedora.im, 17:09:43)
AGREED: 2274006 - RejectedBlocker (Final) - while this is clearly a significant bug for the reporter, no information so far indicates a more widespread issue, there is likely something system-specific about this efibootmgr failure (@adamwill:fedora.im, 17:13:27)

TOPIC:(2272758) Illegal instruction errors in libQt6Core (@adamwill:fedora.im, 17:13:31)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2272758 (@adamwill:fedora.im, 17:13:34)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1585 (@adamwill:fedora.im, 17:13:37)
INFO: Proposed Blocker, gcc, NEW (@adamwill:fedora.im, 17:13:40)
INFO: Ticket vote: FinalBlocker (+1,0,-0) (+frantisekz) (@adamwill:fedora.im, 17:13:42)
INFO: Ticket vote: FinalFreezeException (+3,0,-0) (+geraldosimiao, +adamwill, +ngompa) (@adamwill:fedora.im, 17:13:45)
AGREED: 2272758 - AcceptedBlocker (Final) - this is accepted as a violation of "All release-blocking images must boot in their supported configurations" for Plasma on affected systems. We know affected CPUs are a fairly small minority, but they're still hardware we intend to support, and the fact that multiple people reported this means there really are folks out there who want to run the affected software on the affected CPUs (@adamwill:fedora.im, 17:31:38)

TOPIC:(2274490) nVidia RTX 3000 GPUs are inoperable in Fedora 40 (nouveau) (@adamwill:fedora.im, 17:31:45)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274490 (@adamwill:fedora.im, 17:31:48)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1587 (@adamwill:fedora.im, 17:31:50)
INFO: Proposed Blocker, kernel, NEW (@adamwill:fedora.im, 17:31:54)
AGREED: 2274490 - RejectedBlocker (Final) AcceptedFreezeException (Final) - this is rejected based on current assessment that it seems to affect only some hybrid laptops which already didn't have great nouveau support before 6.8 series. it is annoying on those systems, but not fatal, can be fixed post-release, and we just don't think that's a broad enough impact to block on (@adamwill:fedora.im, 17:46:16)
INFO: 2274061 was accepted as an FE and fixed in 1.13, so we don't really need to worry about that one (@adamwill:fedora.im, 17:46:56)

TOPIC:(2271837) The KDE help center does not show the documentation for KDE applications. (@adamwill:fedora.im, 17:47:17)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2271837 (@adamwill:fedora.im, 17:47:24)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1544 (@adamwill:fedora.im, 17:47:27)
INFO: Accepted Blocker, khelpcenter, MODIFIED (@adamwill:fedora.im, 17:47:31)
INFO: this was partly but not fully addressed in RC-1.13, the fix introduced other problems. assuming we are going to slip for other blockers and do another RC-1.14, we will update to the improved upstream fix that should resolve all issues (@adamwill:fedora.im, 17:54:09)

TOPIC:(2242759) dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key (@adamwill:fedora.im, 17:55:02)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2242759 (@adamwill:fedora.im, 17:55:05)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1435 (@adamwill:fedora.im, 17:55:07)
INFO: Accepted Previous Release Blocker, distribution, NEW (@adamwill:fedora.im, 17:55:10)
INFO: this is still outstanding. it is difficult to fix and hence a waiver candidate, but we're not going that route today as we have other blockers we don't want to waive. any great ideas to fix this are still welcome (@adamwill:fedora.im, 17:57:56)
INFO: we also have an issue with the IoT installer image showing pre-release warnings: https://pagure.io/fedora-iot/issue/57 . That's to do with osbuild, the osbuild team is working on it (@adamwill:fedora.im, 18:06:46)

AGREED: Fedora Linux 40 final is NO GO (@amoloney:fedora.im, 18:13:01)
INFO: The next F40 Final Go/No-Go meeting will be Thursday, 2024-04-18 at 1700 UTC (@amoloney:fedora.im, 18:13:28)
INFO: F340Final shifts to target date #1: Tuesday 2024-04-23 (@amoloney:fedora.im, 18:14:12)
INFO: F40 Final shifts to target date #1: Tuesday 2024-04-23 (@amoloney:fedora.im, 18:14:32)
ACTION: @amoloney to announce decision (@amoloney:fedora.im, 18:15:04)

Meeting ended at 18:17:56 UTC