2024-04-15 @ 16:00 UTC - Fedora 40 Blocker Review Meeting

Hi folks! It’s time for another blocker review meeting. We have 1 proposed blocker (kinda…) and 4 proposed freeze exceptions for Final.

Here is a handy link which should show you the meeting time in your local time.

The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing.

If you have time today, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here.

Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you’ll see links labeled “Vote!” next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. This page has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn’t a clear outcome in the ticket voting yet. THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!

We’ll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they’re not fixed. Information on the release criteria for F40 can be found on the wiki.

For more information about the Blocker and Freeze exception process, check out these links:

And for those of you who are curious how a Blocker Review Meeting works - or how it’s supposed to go and you want to run one - check out the SOP on the wiki.

Have a good day and see you tomorrow!

1 Like

#blocker-review:fedoraproject.org: F40-blocker-review

Meeting started by @adamwill:fedora.im at 16:00:01 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:04)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:00:07)
  3. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:14)
  4. TOPIC:Roll Call (@salimma:fedora.im, 16:01:20)
  5. TOPIC:Introduction (@adamwill:fedora.im, 16:05:06)
    1. INFO: Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. (@adamwill:fedora.im, 16:05:13)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:05:16)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:05:18)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:05:20)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:05:22)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:05:26)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:05:29)
    8. LINK: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria (@adamwill:fedora.im, 16:05:31)
    9. LINK: https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria (@adamwill:fedora.im, 16:05:36)
    10. INFO: for Fedora 40 Final, we have: (@adamwill:fedora.im, 16:05:45)
    11. INFO: 2 Proposed Blockers (@adamwill:fedora.im, 16:05:48)
    12. INFO: 1 Accepted Previous Release Blockers (@adamwill:fedora.im, 16:05:51)
    13. INFO: 4 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:05:53)
    14. INFO: 8 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:05:56)
    15. INFO: coremodule will secretarialize (@adamwill:fedora.im, 16:07:20)
  6. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:07:30)
  7. TOPIC:(2275099) Recording the screencast does not work properly. (@adamwill:fedora.im, 16:07:36)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2275099 (@adamwill:fedora.im, 16:07:39)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1596 (@adamwill:fedora.im, 16:07:42)
    3. INFO: Proposed Blocker, gnome-shell, NEW (@adamwill:fedora.im, 16:07:44)
    4. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+lruzicka) (@adamwill:fedora.im, 16:07:46)
    5. INFO: we will table this bug for more testing during the meeting and proceed for now (@adamwill:fedora.im, 16:17:00)
  8. TOPIC:(2274830) Reinstate network service for Fedora 40 (@adamwill:fedora.im, 16:17:06)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274830 (@adamwill:fedora.im, 16:17:09)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1593 (@adamwill:fedora.im, 16:17:11)
    3. INFO: Proposed Blocker, initscripts, NEW (@adamwill:fedora.im, 16:17:14)
    4. INFO: Ticket vote: FinalBlocker (+2,0,-0) (+geraldosimiao, +ngompa) (@adamwill:fedora.im, 16:17:17)
    5. INFO: this bug is proposed as a blocker for FESCo to considering nominating it, it does not qualify as a blocker under the release criteria, so we will not vote on it (@adamwill:fedora.im, 16:17:41)
  9. TOPIC:Proposed Final freeze exceptions (@adamwill:fedora.im, 16:27:38)
  10. TOPIC:(2274740) fdo-client-linuxapp.service is not enabled by default on IoT (@adamwill:fedora.im, 16:27:41)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274740 (@adamwill:fedora.im, 16:27:44)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1591 (@adamwill:fedora.im, 16:27:47)
    3. INFO: Proposed Freeze Exceptions, fedora-release, ON_QA (@adamwill:fedora.im, 16:27:49)
    4. INFO: Ticket vote: FinalFreezeException (+4,0,-0) (+adamwill, +geraldosimiao, +salimma, +pbrobinson) (@adamwill:fedora.im, 16:27:51)
    5. AGREED: 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it affects the intended configuration of the IoT edition and cannot be fixed with a post-release update (@adamwill:fedora.im, 16:35:48)
  11. TOPIC:(2263334) F40FailsToInstall: network-scripts-teamd (@adamwill:fedora.im, 16:36:04)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2263334 (@adamwill:fedora.im, 16:36:06)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1592 (@adamwill:fedora.im, 16:36:08)
    3. INFO: Proposed Freeze Exceptions, libteam, ON_QA, depends on other bugs (@adamwill:fedora.im, 16:36:11)
    4. INFO: Ticket vote: FinalFreezeException (+1,0,-0) (+geraldosimiao) (@adamwill:fedora.im, 16:36:13)
    5. AGREED: 2263334 - AcceptedFreezeException (Final) - this is accepted on the general principle that we accept clean FTI fixes to ease the upgrade process (@adamwill:fedora.im, 16:42:46)
  12. TOPIC:(2274724) [abrt] nautilus: ptr_array_free(): nautilus killed by SIGABRT (@adamwill:fedora.im, 16:43:10)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274724 (@adamwill:fedora.im, 16:43:14)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1590 (@adamwill:fedora.im, 16:43:16)
    3. INFO: Proposed Freeze Exceptions, nautilus, VERIFIED (@adamwill:fedora.im, 16:43:18)
    4. INFO: Ticket vote: FinalBlocker (+0,0,-3) (-geraldosimiao, -adamwill, -catanzaro) (@adamwill:fedora.im, 16:43:21)
    5. INFO: Ticket vote: FinalFreezeException (+3,0,-0) (+adamwill, +geraldosimiao, +kparal) (@adamwill:fedora.im, 16:43:23)
    6. AGREED: 2274724 - AcceptedFreezeException (Final) - this is accepted as a crasher bug people could at least potentially run into on the Workstation live image. The fix is targeted and well tested. (@adamwill:fedora.im, 16:54:20)
  13. TOPIC:(2274171) parsec 1.4.0 (@adamwill:fedora.im, 16:54:25)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274171 (@adamwill:fedora.im, 16:54:27)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1580 (@adamwill:fedora.im, 16:54:29)
    3. INFO: Proposed Freeze Exceptions, parsec, ON_QA (@adamwill:fedora.im, 16:54:32)
    4. INFO: Ticket vote: FinalFreezeException (+2,0,-0) (+geraldosimiao, +pwhalen) (@adamwill:fedora.im, 16:54:35)
    5. AGREED: 2274171 - RejectedFreezeException (Final) - the proposal here provides no real justification for a freeze exception, and the request is to pull in a major new release with an unclear backwards compatibility status and some slightly odd test results. This is rejected for now, can be proposed again with a clearer justification (@adamwill:fedora.im, 17:03:47)
    6. INFO: let's circle back to our tabled blocker proposal (@adamwill:fedora.im, 17:10:26)
  14. TOPIC:(2275099) Recording the screencast does not work properly. (@adamwill:fedora.im, 17:10:32)
    1. AGREED: 2275099 - RejectedBlocker (Final) - AcceptedFreezeException (Final) - our testing during the meeting suggests this is almost 100% reproducible on libvirt/qemu VMs (especially without 3D passthrough), but not reproducible at all on bare metal. That makes this a conditional violation of the "basic functionality" criterion for default apps and the default panel functionality criterion, but we judge that it's not severe enough to constitute a blocker, but it is bad enough to grant an FE. (@adamwill:fedora.im, 17:43:40)
  15. TOPIC:Accepted blocker review (@adamwill:fedora.im, 17:44:56)
  16. TOPIC:(2242759) dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key (@adamwill:fedora.im, 17:45:04)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2242759 (@adamwill:fedora.im, 17:45:06)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1435 (@adamwill:fedora.im, 17:45:09)
    3. INFO: Accepted Previous Release Blocker, distribution, NEW (@adamwill:fedora.im, 17:45:12)
    4. INFO: we still don't have a great idea for a fix for this, we'll have to discuss further at go/no-go (@adamwill:fedora.im, 17:51:17)
  17. TOPIC:Open floor (@adamwill:fedora.im, 17:56:24)


Meeting ended at 18:00:39 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (195)
  2. @nielsenb:fedora.im (62)
  3. @salimma:fedora.im (46)
  4. @tablepc:matrix.org (30)
  5. @nhanlon:beeper.com (26)
  6. @geraldosimiao:matrix.org (18)
  7. @frantisekz:fedora.im (13)
  8. @zodbot:fedora.im (13)
  9. @nirik:matrix.scrye.com (12)
  10. @decathorpe:fedora.im (7)
  11. @davdunc:fedora.im (4)
  12. @coremodule:fedora.im (2)
  13. @meetbot:fedora.im (2)
  14. @umu:catnip.ee (1)
  15. @conan_kudo:matrix.org (1)