f40-beta-go-no-go-meeting
MINUTES

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

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

Meeting summary

  1. INFO: Purpose of this meeting (@amoloney:fedora.im, 17:04:31)
  2. INFO: The 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:05:18)
  3. INFO: This is determined in a few ways: (@amoloney:fedora.im, 17:05:28)
  4. INFO: info 1. Release candidate compose is available (@amoloney:fedora.im, 17:05:39)
  5. INFO: 2. No remaining blocker bugs (@amoloney:fedora.im, 17:06:02)
  6. INFO: 3. Test matrices are fully competed (@amoloney:fedora.im, 17:06:11)
  7. INFO: Fedora CoreOS and IoT are ready (@amoloney:fedora.im, 17:06:26)
  8. INFO: Topic: Current Status - RC (@amoloney:fedora.im, 17:09:21)
  9. INFO: Release Candidate 1.10 is the proposed F40 Beta release if it satisfies the release criteria, which will be determined in this meeting (@amoloney:fedora.im, 17:15:15)
  10. INFO: Topic: Current Status - Blockers (@amoloney:fedora.im, 17:15:35)
  11. INFO: let's run through the proposed blockers (@adamwill:fedora.im, 17:16:06)
  12. TOPIC:(2270676) ISO boot menu doesn't identify milestone + edition for Server/Everything (@adamwill:fedora.im, 17:16:11)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2270676 (@adamwill:fedora.im, 17:16:13)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1539 (@adamwill:fedora.im, 17:16:16)
    3. INFO: Proposed Blocker, distribution, NEW (@adamwill:fedora.im, 17:16:18)
    4. AGREED: 2270676 - RejectedBlocker (Beta) - this is rejected on the grounds that this screen does not clearly claim that this is a "final" release (it only does not explicitly state that it's Beta), and the user will inevitably encounter several later indications of Beta status, so it is not really confusing (@adamwill:fedora.im, 17:21:58)
  13. TOPIC:(2270681) "About system" in KDE doesn't identify a pre-release system (@adamwill:fedora.im, 17:22:47)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2270681 (@adamwill:fedora.im, 17:22:50)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1540 (@adamwill:fedora.im, 17:22:52)
    3. INFO: Proposed Blocker, kinfocenter, NEW (@adamwill:fedora.im, 17:22:54)
    4. AGREED: 2270681 - RejectedBlocker (Beta) - this is rejected on similar grounds to 2270676: it's been this way for 12 releases without apparently confusing anyone (which is the point of the criterion), it is not clearly claiming to be a final release, and beta status is sufficiently indicated in other ways (@adamwill:fedora.im, 17:26:44)
  14. TOPIC:(2270355) fbx64.efi and mmx64.efi incorrectly signed in 15.8-2 , breaks key management and fallback path boot (@adamwill:fedora.im, 17:26:56)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2270355 (@adamwill:fedora.im, 17:26:58)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1537 (@adamwill:fedora.im, 17:27:01)
    3. INFO: Proposed Blocker, shim, ON_QA (@adamwill:fedora.im, 17:27:03)
    4. INFO: Ticket vote: BetaFreezeException (+3,0,-0) (+kparal, +geraldosimiao, +adamwill) (@adamwill:fedora.im, 17:27:06)
    5. AGREED: 2270355 - RejectedBlocker (Beta) - this is rejected on the grounds that fallback path failing with SB enabled isn't likely to affect too many folks, and we consider that level of impact acceptable for Beta. Note however that this is actually fixed in 1.10 so the determination is academic if we decide to ship it (@adamwill:fedora.im, 17:33:58)
    6. INFO: let's run through accepted blockers that aren't VERIFIED in 1.10 (@adamwill:fedora.im, 17:34:32)
  15. TOPIC:(2247873) U-Boot doesn't find and load the Fedora provided DTBs from /boot/dtb (@adamwill:fedora.im, 17:34:39)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2247873 (@adamwill:fedora.im, 17:34:41)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1471 (@adamwill:fedora.im, 17:34:44)
    3. INFO: Accepted Blocker, uboot-tools, ON_QA (@adamwill:fedora.im, 17:34:46)
    4. AGREED: 2247873 - considered addressed - we are going to consider that the -6 build sufficiently addresses this for Beta. we will write a commonbugs page explaining options in case the bug does cause problems for folks trying to use Beta (flash a newer uboot externally, or use a nightly image with the later uboot) (@adamwill:fedora.im, 18:06:39)
  16. TOPIC:(2269412) Raspberry Pi 4/400: some GUI assets won't load (@adamwill:fedora.im, 18:06:48)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2269412 (@adamwill:fedora.im, 18:06:51)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1534 (@adamwill:fedora.im, 18:06:54)
    3. INFO: Accepted Blocker, mesa, NEW (@adamwill:fedora.im, 18:06:56)
    4. AGREED: 2269412 - waive to F40 Final - this is waived under both "Last minute blocker bugs" and "Difficult to fix blocker bugs" at https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Exceptional_cases - it was discovered late (inevitably, due to previous bugs) and is not straightforward to fix, we are reliant on mesa upstream here and they say it's not a quick fix bug (@adamwill:fedora.im, 18:20:27)
  17. TOPIC:(2242759) dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key (@adamwill:fedora.im, 18:20:41)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2242759 (@adamwill:fedora.im, 18:20:45)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1435 (@adamwill:fedora.im, 18:20:50)
    3. INFO: Accepted Previous Release Blocker, distribution, NEW (@adamwill:fedora.im, 18:20:52)
    4. AGREED: 2242759 - waive to Fedora 40 Final - this is waived for the same reason we waived it before: it's a complex bug and we still don't really have a great idea for fixing it. Nothing we can commit to landing in a week or two, so it is not appropriate for it to hold up the Beta release. We really need someone to have an idea to fix it soon, or we'll have to declare it unfixable (@adamwill:fedora.im, 18:29:32)
    5. ACTION: Aoife Moloney to keep track and make sure this doesn't get forgotten about again (@adamwill:fedora.im, 18:29:44)
    6. INFO: with the decisions taken above, all outstanding blockers are addressed or waived (@adamwill:fedora.im, 18:30:30)
    7. LINK: https://gitlab.com/redhat/centos-stream/rpms/dnf-plugins-core/-/blob/c9s/0006-Fix-boot-time-derivation-for-systems-with-no-rtc.patch?ref_type=heads (@nhanlon:beeper.com, 18:32:01)
    8. INFO: All accepted blockers have been addressed for RC 1.10 beta (@amoloney:fedora.im, 18:37:51)
    9. INFO: Topic: Current Status - Test Matrices (@amoloney:fedora.im, 18:42:07)
    10. INFO: Link https://fedoraproject.org/wiki/Category:Fedora_40_Test_Results (@amoloney:fedora.im, 18:42:24)
    11. INFO: with 1.9 and 1.10 results combined, coverage is almost complete, except cloud ec2 testing (@adamwill:fedora.im, 18:46:37)
    12. INFO: ec2 tests are being run on both aarch64 and x86_64, there will be a slight pause in the meeting to allow these tests to complete before continuing (@amoloney:fedora.im, 18:50:34)
    13. INFO: Toic: Waiting (@amoloney:fedora.im, 18:50:48)
    14. INFO: Topic: Waiting (@amoloney:fedora.im, 18:50:55)
    15. INFO: There is sufficient test coverage on the Beta RC to continue the meeting (@amoloney:fedora.im, 19:04:20)
    16. INFO: Topic: Fedora CoreOS & IoT check-in (@amoloney:fedora.im, 19:05:05)
    17. INFO: IoT team has signed off on 20240319.2 for Beta release, CoreOS team is confident they can have the 'next' stream with F40 content next week (@adamwill:fedora.im, 19:14:51)
    18. INFO: Release Candidate - 1.10 (@amoloney:fedora.im, 19:18:04)
    19. INFO: The RC 1.10 is the current release candidate, is there anything missing? (@amoloney:fedora.im, 19:18:48)
    20. INFO: Topic: Go/No-Go Decision (@amoloney:fedora.im, 19:23:43)
    21. INFO: I will now poll each team. Please reply 'Go' or 'No Go' (@amoloney:fedora.im, 19:24:12)
    22. INFO: Agreed: Fedora Linux 40 Beta is GO (@amoloney:fedora.im, 19:25:40)
    23. INFO: Fedora Linux 40 Beta will release on the current target date 2024-03-26 (@amoloney:fedora.im, 19:26:05)
    24. ACTION: @amoloney to announce decision (@amoloney:fedora.im, 19:26:48)
    25. INFO: Topic: Open Floor (@amoloney:fedora.im, 19:27:00)
    26. ACTION: @amoloney to open a ticket with FESCo highlighting the short time between Beta release and Final Freeze to discuss the possibility of delaying Final Freeze (@amoloney:fedora.im, 19:35:42)


Meeting ended at 19:51:42 UTC

Action items

  1. Aoife Moloney to keep track and make sure this doesn't get forgotten about again
  2. @amoloney to announce decision
  3. @amoloney to open a ticket with FESCo highlighting the short time between Beta release and Final Freeze to discuss the possibility of delaying Final Freeze


People present (lines said)

  1. @adamwill:fedora.im (181)
  2. @amoloney:fedora.im (98)
  3. @nirik:matrix.scrye.com (51)
  4. @geraldosimiao:matrix.org (48)
  5. @sgallagh:fedora.im (27)
  6. @zodbot:fedora.im (20)
  7. @farribeiro:matrix.org (18)
  8. @lruzicka:matrix.org (17)
  9. @nhanlon:beeper.com (17)
  10. @pbrobinson:fedora.im (16)
  11. @pwhalen:fedora.im (12)
  12. @jbwillia:fedora.im (10)
  13. @coremodule:fedora.im (8)
  14. @copperi:fedora.im (8)
  15. @bittin:fedora.im (7)
  16. @jnsamyak:matrix.org (5)
  17. @dustymabe:matrix.org (5)
  18. @frantisekz:fedora.im (3)
  19. @meetbot:fedora.im (2)




Meetbot Logs © 2021-2022 Fedora Websites and Apps Team (Sources)