2024-03-11 @ **16:00** UTC - Fedora 40 Blocker Review Meeting

Project Discussion
, , , ,
1

Hi folks! It’s time for another blocker review meeting. We have 2 proposed blockers and 5 proposed freeze exceptions for Beta, and 4 proposed blockers for Final.

Please note that summer time starts in most of North America on Sunday, and we follow that time for these meetings, so the meeting time in UTC has changed. If you put your clocks forward this Sunday, the meeting will be at the same local time as it was last week. If you do not, the meeting will be one hour earlier than it was last week. You can always run date -u to see the current UTC time and check, if you’re not sure. 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 this weekend, 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 weekend and see you on Monday!

1 Like
2

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:31)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:06:34)
    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:06:41)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:06:43)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:06:46)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:06:49)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:06:52)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:06:56)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:06:59)
    8. LINK: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria (@adamwill:fedora.im, 16:07:01)
    9. LINK: https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria (@adamwill:fedora.im, 16:07:04)
    10. INFO: for Beta, we have: (@adamwill:fedora.im, 16:07:06)
    11. INFO: 1 Proposed Blockers (@adamwill:fedora.im, 16:07:13)
    12. INFO: 5 Accepted Blockers (@adamwill:fedora.im, 16:07:16)
    13. INFO: 1 Accepted 0-day Blockers (@adamwill:fedora.im, 16:07:19)
    14. INFO: 1 Accepted Previous Release Blockers (@adamwill:fedora.im, 16:07:21)
    15. INFO: 8 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:07:24)
    16. INFO: 6 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:07:26)
    17. INFO: for Final, we have: (@adamwill:fedora.im, 16:07:31)
    18. INFO: 7 Proposed Blockers (@adamwill:fedora.im, 16:07:38)
    19. INFO: coremodule will secretarialize (@adamwill:fedora.im, 16:10:43)
  3. TOPIC:Proposed Beta blockers (@adamwill:fedora.im, 16:11:32)
  4. TOPIC:(2170957) parsec service fails to start on Fedora IoT 37 upgraded from F36 IoT (@adamwill:fedora.im, 16:11:40)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2170957 (@adamwill:fedora.im, 16:11:43)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1510 (@adamwill:fedora.im, 16:11:47)
    3. INFO: Proposed Blocker, parsec, ON_QA (@adamwill:fedora.im, 16:11:50)
  5. TOPIC:Proposed Beta freeze exceptions (@adamwill:fedora.im, 16:23:05)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2267754 (@adamwill:fedora.im, 16:24:33)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1493 (@adamwill:fedora.im, 16:24:37)
    3. INFO: Proposed Freeze Exceptions, distribution, NEW, depends on other bugs (@adamwill:fedora.im, 16:24:39)
    4. INFO: Ticket vote: BetaFreezeException (+1,0,-2) (+ngompa, -nielsenb, -geraldosimiao) (@adamwill:fedora.im, 16:24:42)
  6. TOPIC:(2264986) gcc 14.0.1-0.7 break mesa build (@adamwill:fedora.im, 16:31:04)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264986 (@adamwill:fedora.im, 16:31:07)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1501 (@adamwill:fedora.im, 16:31:10)
    3. INFO: Proposed Freeze Exceptions, gcc, ON_QA (@adamwill:fedora.im, 16:31:13)
    4. INFO: Ticket vote: BetaFreezeException (+2,0,-2) (+nixuser, +frantisekz, -nielsenb, -geraldosimiao) (@adamwill:fedora.im, 16:31:15)
  7. TOPIC:(2265402) [abrt] gnome-shell: meta_group_new(): gnome-shell killed by SIGABRT (@adamwill:fedora.im, 16:38:44)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2265402 (@adamwill:fedora.im, 16:38:47)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1498 (@adamwill:fedora.im, 16:38:50)
    3. INFO: Proposed Freeze Exceptions, gnome-shell, POST (@adamwill:fedora.im, 16:38:55)
  8. TOPIC:(2170957) parsec service fails to start on Fedora IoT 37 upgraded from F36 IoT (@adamwill:fedora.im, 16:44:10)
    1. AGREED: 2170957 - RejectedBlocker (Beta), AcceptedBlocker (Final), AcceptedFreezeException (Beta) - this is rejected as a blocker for Beta but accepted as a blocker for Final because it violates the "all services must work by default" criterion which is for Final, not Beta. It's accepted as a BetaFE as it would obviously be great to make sure upgrades to Beta do not break a default service (@adamwill:fedora.im, 16:44:24)
  9. TOPIC:(2267754) Include GNOME Shell (etc.) 46 rc1 in Fedora 40 Beta (@adamwill:fedora.im, 16:44:38)
    1. AGREED: 2267754 - RejectedFreezeException (Beta) - we generally are willing to take these if they can land sufficiently early, but in this case, the update is not ready yet and we already know there would be a significant bug if one were prepared today, so it seems clear that this must be rejected (@adamwill:fedora.im, 16:44:52)
  10. TOPIC:(2264986) gcc 14.0.1-0.7 break mesa build ✅ 1 (@adamwill:fedora.im, 16:45:01)
  11. TOPIC:(2264986) gcc 14.0.1-0.7 break mesa build (@adamwill:fedora.im, 16:45:14)
    1. AGREED: 264986 - RejectedFreezeException (Beta) - this is rejected as there is no clear rationale for why it's needed. we do not need to build mesa for F40 Beta currently, and the bug does not indicate that any other package affected by this bug currently needs building for Beta. (@adamwill:fedora.im, 16:45:49)
  12. TOPIC:(2265402) [abrt] gnome-shell: meta_group_new(): gnome-shell killed by SIGABRT (@adamwill:fedora.im, 16:46:01)
    1. AGREED: 2265402 - AccepteedFreezeException (Beta) - this is accepted as it could affect folks trying to run Thunderbird from the live session, or immediately after install and without first updating mutter. This will only be fixed if the fix can be backported in an isolated fashion on top of 46-beta and tested (@adamwill:fedora.im, 16:51:17)
  13. TOPIC:(2268583) [abrt] gnome-software: gtk_widget_get_parent_muxer.constprop.0(): gnome-software killed by SIGSEGV (@adamwill:fedora.im, 16:51:33)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2268583 (@adamwill:fedora.im, 16:51:37)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1513 (@adamwill:fedora.im, 16:51:39)
    3. INFO: Proposed Freeze Exceptions, gtk4, NEW (@adamwill:fedora.im, 16:51:42)
    4. AGREED: 2268583 - AcceptedFreezeException (Beta) - this is accepted on the basis that fixing crashes in default-installed apps is definitely desirable for Beta. we note that we cannot accept the whole of GNOME 46 RC to fix this (the new gtk4 is currently bundled in that update); either gtk4 would have to be split out from that update somehow, or the xevent issue would have to be resolved and the GNOME 46 RC FE ticket re-voted (probably only after another slip) (@adamwill:fedora.im, 17:06:52)
  14. TOPIC:(2268951) Ship updated kiwi to enable s390x Fedora Cloud image builds (@adamwill:fedora.im, 17:07:01)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2268951 (@adamwill:fedora.im, 17:07:03)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1511 (@adamwill:fedora.im, 17:07:05)
    3. INFO: Proposed Freeze Exceptions, kiwi, MODIFIED (@adamwill:fedora.im, 17:07:08)
    4. INFO: Ticket vote: BetaFreezeException (+0,0,-1) (-nielsenb) (@adamwill:fedora.im, 17:07:11)
    5. AGREED: 2268951 - AcceptedFreezeException (Beta) - this is useful/needed for the attempt to land https://fedoraproject.org/wiki/Changes/KiwiBuiltCloudImages , and as it's an update to kiwi itself it can't break anything else (@adamwill:fedora.im, 17:15:29)
  15. TOPIC:(2268704) Plugin doesn't work on KDE Plasma 6 (@adamwill:fedora.im, 17:15:35)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2268704 (@adamwill:fedora.im, 17:15:38)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1507 (@adamwill:fedora.im, 17:15:40)
    3. INFO: Proposed Freeze Exceptions, plasma-wallpapers-dynamic, ON_QA (@adamwill:fedora.im, 17:15:43)
    4. INFO: Ticket vote: BetaFreezeException (+1,0,-0) (+nielsenb) (@adamwill:fedora.im, 17:15:45)
    5. AGREED: 2268704 - AcceptedFreezeException (Beta) - this is accepted to fix the upgrade experience for folks with this plugin installed before the 0-day update push. It's not a very critical problem, but it's also a low-risk fix, and F40 KDE is getting some public attention ATM so we'd like the experience to be as smooth as possible for early jumpers (@adamwill:fedora.im, 17:25:45)
  16. TOPIC:(2268497) F40 FE: KDE Plasma 6.0.1 (@adamwill:fedora.im, 17:25:53)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2268497 (@adamwill:fedora.im, 17:25:55)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1502 (@adamwill:fedora.im, 17:25:58)
    3. INFO: Proposed Freeze Exceptions, plasma-workspace, NEW (@adamwill:fedora.im, 17:26:00)
    4. INFO: Ticket vote: BetaFreezeException (+2,1,-1) (+frantisekz, +ngompa, geraldosimiao, -nielsenb) (@adamwill:fedora.im, 17:26:02)
    5. AGREED: 268497 - AcceptedFreezeException (Beta) - this is accepted, but with the caveat that we only intend to pull it in if there's another slip. it's too risky to pull it in now for something we intend to sign off on Thursday. This also applies to a 6.0.2 build, if it is ready by Friday (the last day we would want to land this if we were targeting next Thursday) (@adamwill:fedora.im, 17:35:56)
  17. TOPIC:(2264975) F40FailsToInstall: visidata (@adamwill:fedora.im, 17:36:08)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2264975 (@adamwill:fedora.im, 17:36:10)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1509 (@adamwill:fedora.im, 17:36:15)
    3. INFO: Proposed Freeze Exceptions, visidata, ON_QA, depends on other bugs (@adamwill:fedora.im, 17:36:18)
    4. INFO: Ticket vote: BetaFreezeException (+2,0,-0) (+frantisekz, +nielsenb) (@adamwill:fedora.im, 17:36:20)
    5. AGREED: 2264975 - AcceptedFreezeException (Beta) - this is accepted as we usually accept straightforward FTI fixes as Beta FE to smooth the upgrade process for early upgraders (@adamwill:fedora.im, 17:39:00)
  18. TOPIC:Accepted Blocker review (@adamwill:fedora.im, 17:39:13)
    1. INFO: we are basically waiting on ARM. the outstanding unaddressed blockers are 2267968 and 2247873 which are both ARM issues, 2242759 which is another old ARM (effectively) issue we kinda forgot about, and the two shim blockers, 2113005 and 2259264 (@adamwill:fedora.im, 17:40:27)
    2. INFO: I would assume we will waive the shim blockers if a shim build is still not ready in time, so...we're waiting on ARM (@adamwill:fedora.im, 17:40:43)
    3. INFO: we are worried that there's a pattern indicating we don't have sufficient ability to fix ARM blockers in a timely fashion, but unsure what to do about this. we've informally noted it to FESCo in this meeting (@adamwill:fedora.im, 18:00:03)
  19. TOPIC:Open floor (@adamwill:fedora.im, 18:00:27)


Meeting ended at 18:17:19 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (241)
  2. @conan_kudo:matrix.org (66)
  3. @nielsenb:fedora.im (46)
  4. @sgallagh:fedora.im (38)
  5. @geraldosimiao:matrix.org (36)
  6. @lruzicka:matrix.org (23)
  7. @frantisekz:fedora.im (16)
  8. @zodbot:fedora.im (14)
  9. @humaton:fedora.im (12)
  10. @pwhalen:fedora.im (9)
  11. @coremodule:fedora.im (8)
  12. @amoloney:fedora.im (6)
  13. @nhanlon:beeper.com (4)
  14. @farribeiro:matrix.org (4)
  15. @thebeanogamer:fedora.im (4)
  16. @siosm:matrix.org (4)
  17. @meetbot:fedora.im (2)
  18. @mmartinv:matrix.org (1)
  19. @farchord:matrix.org (1)
  20. @supakeen:fedora.im (1)
  21. @timaeos:matrix.nexaeos.io (1)
  22. @kparal:matrix.org (1)


1 Like
3

Note - the minutes read a bit weird because I used the wrong syntax for agreements for the first few issues, so they didn’t get logged. Partway through the meeting I realized the mistake and had to go back to the initial topics and post the agreements.

1 Like