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

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

INFO: 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:04:00)
INFO: This is determined in a few ways: (@amoloney:fedora.im, 17:04:13)
INFO: 1. Release candidate compose is available (@amoloney:fedora.im, 17:04:38)
INFO: 2. No remaining blocker bugs (@amoloney:fedora.im, 17:04:50)
INFO: 3.Test matrices are fully complete (@amoloney:fedora.im, 17:05:06)
INFO: 4. Fedora CoreOS & IoT are ready (@amoloney:fedora.im, 17:05:17)

INFO: https://dl.fedoraproject.org/pub/alt/stage/40_RC-1.14/ is the current RC (@adamwill:fedora.im, 17:06:29)
INFO: RC 1.14 is the release candidate that we will decide if Fedora Linux 40 will release with (@amoloney:fedora.im, 17:07:05)

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

TOPIC:(2275209) Intended final backgrounds for Fedora 40 are not included (@adamwill:fedora.im, 17:08:33)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2275209 (@adamwill:fedora.im, 17:08:38)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1597 (@adamwill:fedora.im, 17:08:41)
INFO: Proposed Blocker, f40-backgrounds, MODIFIED (@adamwill:fedora.im, 17:08:44)
INFO: Ticket vote: FinalBlocker (+0,0,-5) (-augenauf, -catanzaro, -kevin, -geraldosimiao, -lruzicka) (@adamwill:fedora.im, 17:08:47)
INFO: Ticket vote: FinalFreezeException (+3,0,-2) (+augenauf, +lruzicka, +kparal, -catanzaro, -geraldosimiao) (@adamwill:fedora.im, 17:08:52)
AGREED: 2275209 - RejectedBlocker (Final) - this is rejected on the grounds that the design team now agrees the new backgrounds arrived too late, which makes the Beta backgrounds once more the "proposed final Fedora artwork". See https://gitlab.com/groups/fedora/design/-/epics/32#note_1866027989 (@adamwill:fedora.im, 17:14:17)

TOPIC:(2275855) CVE-2024-2961 glibc: Out of bounds write in iconv may lead to remote code execution [fedora-all] (@adamwill:fedora.im, 17:14:26)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2275855 (@adamwill:fedora.im, 17:14:28)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1600 (@adamwill:fedora.im, 17:14:30)
INFO: Proposed Blocker, glibc, ASSIGNED (@adamwill:fedora.im, 17:14:34)
AGREED: 2275855 - Accepted0Day (Final) - this is accepted as a violation of the CVE criterion, but as a 0Day blocker because in the glibc maintainer's expert opinion, it is not likely to be exploitable against typical actions on live or installer media, so it is fine to resolve it with an update rather than a new candidate compose (@adamwill:fedora.im, 17:26:46)
INFO: let's revisit our outstanding 0-day blocker (@adamwill:fedora.im, 17:27:16)

TOPIC:(2274830) Reinstate network service for Fedora 40 (@adamwill:fedora.im, 17:27:27)

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274830 (@adamwill:fedora.im, 17:27:29)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1593 (@adamwill:fedora.im, 17:27:31)
INFO: Accepted 0-day Blocker, initscripts, ON_QA (@adamwill:fedora.im, 17:27:34)
INFO: the update is queued for stable, so this is fine (@adamwill:fedora.im, 17:27:54)
INFO: let's revisit our outstanding previous release blocker (@adamwill:fedora.im, 17:28:02)

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

LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2242759 (@adamwill:fedora.im, 17:28:13)
LINK: https://pagure.io/fedora-qa/blocker-review/issue/1435 (@adamwill:fedora.im, 17:28:15)
INFO: Accepted Previous Release Blocker, distribution, NEW (@adamwill:fedora.im, 17:28:18)
AGREED: 2242759 - waived as a "difficult to fix blocker bug" per https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases - this is waived to Fedora 41 Beta for now, as we still have no clear solution proposed or firm timeline for one (@adamwill:fedora.im, 17:38:43)
INFO: we have no blockers that disqualify RC-1.14. We have two accepted 0-day blockers which are clearly on track to be fixed by release day (@adamwill:fedora.im, 17:39:18)

LINK: link https://fedoraproject.org/wiki/Category:Fedora_40_Test_Result (@amoloney:fedora.im, 17:40:54)
LINK: https://fedoraproject.org/wiki/Test_Results:Current_Summary (@conan_kudo:matrix.org, 17:42:32)
INFO: we are missing macOS dual boot test due to nobody having the hardware, we will have to trust that the pass in February is still valid (@adamwill:fedora.im, 18:03:25)
INFO: a couple of other tests are missing because they failed in openQA, the failures just look like blips, the same tests have since passed on nightlies that are identical to the RC. i'm re-running the failed tests ATM (@adamwill:fedora.im, 18:04:13)
INFO: other than those issues the matrices are substantially complete, i think we can consider the coverage complete (@adamwill:fedora.im, 18:04:35)

LINK: https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-40-20240417.0/ (@coremodule:fedora.im, 18:07:58)
LINK: https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=40&build=Fedora-IoT-40-20240417.0&groupid=1 (@adamwill:fedora.im, 18:08:14)
LINK: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_40_RC_20240417.0_General (@adamwill:fedora.im, 18:09:21)

INFO: I will now poll each team for a Go or No-Go decision. (@amoloney:fedora.im, 18:12:00)
AGREED: Fedora Linux 40 Final is GO (@amoloney:fedora.im, 18:13:47)
INFO: Fedora Linux 40 Final will release on the current target date (2024-04-23 (@amoloney:fedora.im, 18:14:47)

Meeting ended at 18:19:25 UTC