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

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

Meeting summary

  1. INFO: We've done some early roll call, and present is nirik FrantiĊĦek Zatloukal Stephen Gallagher sircharles lruzicka (@amoloney:fedora.im, 17:04:25)
  2. TOPIC:Roll Call (@amoloney:fedora.im, 17:04:40)
    1. 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:06:47)
    2. INFO: correction - we are determining F41 Beta is ready for shipment (@amoloney:fedora.im, 17:07:28)
    3. INFO: The F41 Beta is determined release ready in a few ways (@amoloney:fedora.im, 17:08:00)
    4. INFO: 1. Release candidate compose is available (@amoloney:fedora.im, 17:08:31)
    5. INFO: 2. No remaining blocker bugs (@amoloney:fedora.im, 17:08:44)
    6. INFO: 3. Test matrices are fully completed (@amoloney:fedora.im, 17:08:59)
    7. INFO: 4. Fedora CoreOS and IoT are ready (@amoloney:fedora.im, 17:09:11)
  3. TOPIC:Current Status - RC (@amoloney:fedora.im, 17:10:08)
  4. TOPIC:Current Status - Blockers (@amoloney:fedora.im, 17:11:50)
    1. LINK: link https://qa.fedoraproject.org/blockerbugs/milestone/41/beta/buglist (@amoloney:fedora.im, 17:12:09)
    2. INFO: 2 Proposed Blockers (@frantisekz:fedora.im, 17:14:37)
    3. INFO: 2 Accepted Blockers (@frantisekz:fedora.im, 17:14:41)
    4. INFO: 0 Accepted 0-day Blockers (@frantisekz:fedora.im, 17:14:46)
    5. INFO: 1 Accepted Previous Release Blockers (@frantisekz:fedora.im, 17:14:50)
    6. INFO: 4 Proposed Freeze Exceptions (@frantisekz:fedora.im, 17:14:54)
    7. INFO: 7 Accepted Freeze Exceptions (@frantisekz:fedora.im, 17:14:57)
  5. TOPIC:Proposed Beta blockers (@frantisekz:fedora.im, 17:15:28)
  6. TOPIC:(2311964) Discover does not discover upgrades to Fedora 41. (@frantisekz:fedora.im, 17:15:40)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2311964 (@frantisekz:fedora.im, 17:15:42)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1659 (@frantisekz:fedora.im, 17:15:46)
    3. INFO: Proposed Blocker, plasma-discover, NEW (@frantisekz:fedora.im, 17:15:50)
    4. AGREED: 2311964 - RejectedBlocker (Beta) - this doesn't violate the beta criterion as Discover isn't listed as recommended on https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-release/ (@frantisekz:fedora.im, 17:38:05)
  7. TOPIC:(2311907) Anaconda crashes when an error occurs and should be reported. (@frantisekz:fedora.im, 17:38:30)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2311907 (@frantisekz:fedora.im, 17:38:35)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1657 (@frantisekz:fedora.im, 17:38:39)
    3. INFO: Proposed Blocker, python3.13, ASSIGNED (@frantisekz:fedora.im, 17:38:44)
    4. AGREED: 2311907 - RejectedBlocker (Beta) - we can't reproduce it using real crashes, and we have a strong suspicion that the issue would occur only in special code-path for testing the crash reporting feature in Anaconda (@frantisekz:fedora.im, 18:01:07)
  8. TOPIC:(2311936) pyanaconda.modules.common.errors.storage.UnknownDeviceError: Volume0_0 (@frantisekz:fedora.im, 18:01:30)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2311936 (@frantisekz:fedora.im, 18:01:34)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1658 (@frantisekz:fedora.im, 18:01:39)
    3. INFO: Proposed Blocker, anaconda, ASSIGNED (@frantisekz:fedora.im, 18:01:43)
    4. INFO: the criterion doesn't apply to Beta release, on purpose, and the wiki test matrix was updated accordingly (@frantisekz:fedora.im, 18:05:42)
  9. TOPIC:Accepted Beta blockers (@frantisekz:fedora.im, 18:07:05)
  10. TOPIC:(2282171) gsk: vulkan renderer causes gtk4 apps to crash on resize operations on Raspberry Pi 4 and 400 (@frantisekz:fedora.im, 18:07:21)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2282171 (@frantisekz:fedora.im, 18:07:28)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1605 (@frantisekz:fedora.im, 18:07:31)
    3. INFO: Accepted Blocker, bcm283x-firmware, ASSIGNED (@frantisekz:fedora.im, 18:07:35)
    4. AGREED: 2282171 - RejectedBlocker (Beta) AcceptedBlocker (Final) - this wasn't deemed worthy to block the beta release on, but we agreed that the final release has to have a fix for the issue. We also accept it as a common bug to have a documented workaround. (@frantisekz:fedora.im, 18:20:30)
  11. TOPIC:(2283978) Raspberry Pi 4 automatically suspends when idle, claims to support suspend, but can't be woken up (@frantisekz:fedora.im, 18:20:52)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2283978 (@frantisekz:fedora.im, 18:20:57)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1607 (@frantisekz:fedora.im, 18:21:02)
    3. INFO: Accepted Blocker, kernel, ASSIGNED (@frantisekz:fedora.im, 18:21:06)
    4. AGREED: 2283978 - waive to F41 Final - this is waived under "Difficult to fix blocker bugs" at https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases , on the advice of the maintainers involved (see the bug for details) (@frantisekz:fedora.im, 18:28:49)
    5. INFO: those were all accepted blockers, circling back to the proposed one (@frantisekz:fedora.im, 18:29:35)
  12. TOPIC:Proposed Beta Blockers (@frantisekz:fedora.im, 18:30:29)
  13. TOPIC:(2311964) Discover does not discover upgrades to Fedora 41. (@frantisekz:fedora.im, 18:30:42)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2311964 (@frantisekz:fedora.im, 18:30:46)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1659 (@frantisekz:fedora.im, 18:30:50)
    3. INFO: Proposed Blocker, plasma-discover, NEW (@frantisekz:fedora.im, 18:30:53)
    4. INFO: we aren't revoting the 2311964 (@frantisekz:fedora.im, 18:44:20)
  14. TOPIC:Accepted Previous Release Blockers (@frantisekz:fedora.im, 18:46:03)
  15. TOPIC:(2242759) dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key (@frantisekz:fedora.im, 18:46:16)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2242759 (@frantisekz:fedora.im, 18:46:18)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1601 (@frantisekz:fedora.im, 18:46:22)
    3. INFO: Accepted Previous Release Blocker, distribution, NEW (@frantisekz:fedora.im, 18:46:25)
    4. AGREED: 2242759 - RejectedBlocker (Beta) - this is dropped as hard to fix bug as we don't have proposals how to properly fix the issue, and there is no point in rolling this one from release to release. (@frantisekz:fedora.im, 18:53:00)
    5. INFO: All blockers have been addressed for RC 1.2 beta (@amoloney:fedora.im, 18:54:15)
    6. INFO: Current Status - Test Matrices (@amoloney:fedora.im, 18:54:43)
    7. LINK: https://fedoraproject.org/wiki/Category:Fedora_41_Test_Results (@amoloney:fedora.im, 18:57:02)
  16. TOPIC:Status - Waiting (@amoloney:fedora.im, 19:05:44)
    1. INFO: a number of tests are being run to confirm test coverage. The meeting will resume once test results are complete (@amoloney:fedora.im, 19:06:33)
    2. ACTION: @amoloney to coordinate with websites so that the correct information is available on release day that some deliverables are missing from the proposed rc 1.2, but some will be available from the nightly tree and available post release from here (@amoloney:fedora.im, 19:55:41)
    3. INFO: Test matrices are complete for RC 1.2 beta and we have sufficient coverage. The only coverage we were unable to provide at this time is testing on sas / hw raid as there was no available hardware. (@amoloney:fedora.im, 20:00:02)
    4. INFO: We also have a number of missing deliverables from RC 1.2, captured in the failed-compose issue https://pagure.io/releng/failed-composes/issue/6956#comment-931510 . Availability of some of these deliverables will be from the nightly tree and will be noted at beta release time (@amoloney:fedora.im, 20:01:44)
  17. TOPIC:Go/No-Go Decision (@amoloney:fedora.im, 20:02:15)
    1. INFO: Fedora Linux 41 Beta is GO and will be shipped on Tuesday 17th September 2024 (@amoloney:fedora.im, 20:03:45)
  18. TOPIC:Open Floor (@amoloney:fedora.im, 20:04:24)


Meeting ended at 20:06:01 UTC

Action items

  1. @amoloney to coordinate with websites so that the correct information is available on release day that some deliverables are missing from the proposed rc 1.2, but some will be available from the nightly tree and available post release from here


People present (lines said)

  1. @adamwill:fedora.im (141)
  2. @frantisekz:fedora.im (122)
  3. @nirik:matrix.scrye.com (100)
  4. @amoloney:fedora.im (80)
  5. @lruzicka:matrix.org (41)
  6. @sgallagh:fedora.im (25)
  7. @geraldosimiao:matrix.org (14)
  8. @zodbot:fedora.im (10)
  9. @conan_kudo:matrix.org (7)
  10. @pwhalen:fedora.im (6)
  11. @farchord:matrix.org (3)
  12. @meetbot:fedora.im (2)
  13. @farribeiro:matrix.org (1)
  14. @mattdm:fedora.im (1)
  15. @lbrabec:matrix.org (1)