2024-09-03 (**TUESDAY**) @ 16:00 UTC - Fedora 41 Blocker Review Meeting

Project Discussion
, ,
1

(NOTE: I’m posting this retrospectively, but it’s still written in present tense. Sorry. Announcement for 2024-09-16 coming soon).

Hi folks! It’s time for a Fedora 41 blocker review meeting! As Monday is a holiday in North America, let’s do it on Tuesday instead. We have 7 proposed freeze exceptions for Beta.

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!

Especially since we have so many proposed FEs right now, it would really help make the meeting shorter if people can vote on them today.

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 holiday weekend and see you on Tuesday!

1 Like
2

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:47)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:03:09)
    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:03:20)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:03:22)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:03:25)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:03:27)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:03:29)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:03:32)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:03:35)
    8. LINK: https://fedoraproject.org/wiki/Fedora_41_Beta_Release_Criteria (@adamwill:fedora.im, 16:03:38)
    9. LINK: https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria (@adamwill:fedora.im, 16:03:40)
    10. INFO: for Beta, we have 2 proposed blockers and 2 proposed FEs (@adamwill:fedora.im, 16:04:00)
    11. INFO: no proposals for Final as of now (@adamwill:fedora.im, 16:04:15)
    12. INFO: František Zatloukal will secretarialize (@adamwill:fedora.im, 16:04:33)
  3. TOPIC:Proposed Beta blockers (@adamwill:fedora.im, 16:04:47)
  4. TOPIC:(2308952) The updates-testing repo isn't enabled by default (@adamwill:fedora.im, 16:04:55)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2308952 (@adamwill:fedora.im, 16:04:58)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1633 (@adamwill:fedora.im, 16:05:00)
    3. INFO: Proposed Blocker, fedora-repos, NEW (@adamwill:fedora.im, 16:05:02)
    4. INFO: Ticket vote: BetaBlocker (+2,2,-0) (+lruzicka, +pbrobinson, kparal, nielsenb) (@adamwill:fedora.im, 16:05:05)
    5. INFO: Ticket vote: BetaFreezeException (+1,0,-0) (+adamwill) (@adamwill:fedora.im, 16:05:08)
    6. AGREED: 2308952 - punt (delay decision) - as this is already accepted as an FE and the blocker status appears to be subject to FESCo jumping all over it, we'll delay the decision on blocker status while that happens. in any case the bug will shortly be fixed. (@adamwill:fedora.im, 16:12:56)
  5. TOPIC:(2309337) Synchronous Exception on boot (@adamwill:fedora.im, 16:13:17)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2309337 (@adamwill:fedora.im, 16:13:21)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1637 (@adamwill:fedora.im, 16:13:24)
    3. INFO: Proposed Blocker, grub2, NEW (@adamwill:fedora.im, 16:13:26)
    4. INFO: Ticket vote: BetaBlocker (+0,0,-2) (-nielsenb, -ngompa) (@adamwill:fedora.im, 16:13:29)
    5. AGREED: 2309337 - punt (delay decision) - there's some ambiguity around the ARM supported hardware list, here, and we would like to see additional testing to see if other SystemReady hardware is affected (@adamwill:fedora.im, 16:30:05)
    6. ACTION: adamw to mail arm@ list about reconciling the supported HW lists (@adamwill:fedora.im, 16:30:16)
  6. TOPIC:Proposed Beta freeze exceptions (@adamwill:fedora.im, 16:30:34)
  7. TOPIC:(2297927) rpmsign broken: error: sign_hash failed (@adamwill:fedora.im, 16:31:01)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2297927 (@adamwill:fedora.im, 16:31:04)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1630 (@adamwill:fedora.im, 16:31:06)
    3. INFO: Proposed Freeze Exceptions, ima-evm-utils, ON_QA (@adamwill:fedora.im, 16:31:09)
    4. INFO: Ticket vote: BetaFreezeException (+1,0,-0) (+ngompa) (@adamwill:fedora.im, 16:31:12)
    5. AGREED: 2297927 - AcceptedFE (Beta) - this is accepted as it potentially has consequences during compose of IoT and upgrade of IoT systems to Beta, per Peter (@adamwill:fedora.im, 16:41:48)
  8. TOPIC:(2304328) Multiple issues migrating from ostree-boot to rust-bootupd (@adamwill:fedora.im, 16:41:54)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2304328 (@adamwill:fedora.im, 16:41:57)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1638 (@adamwill:fedora.im, 16:41:59)
    3. INFO: Proposed Freeze Exceptions, rust-bootupd, NEW (@adamwill:fedora.im, 16:42:01)
    4. AGREED: 2304328 - punt (delay decision) - we're generally inclined to +1 appropriate and scoped fixes for bootupd, but this seems like a very vague ticket, we would like to ask travier for more clarity on which of the 7.5 listed issues are considered in scope for fixing here (@adamwill:fedora.im, 16:55:39)
  9. TOPIC:Accepted Beta blockers (@adamwill:fedora.im, 16:56:02)
    1. INFO: as a reminder, we're not generally revoting these, just checking in on status (@adamwill:fedora.im, 16:56:12)
  10. TOPIC:(2276839) Fedora 41: Workstation live x86_64 image exceeds maximum size (@adamwill:fedora.im, 16:56:19)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2276839 (@adamwill:fedora.im, 16:56:21)
    2. INFO: Accepted Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 16:56:24)
    3. INFO: we haven't been able to reduce the size. Conan Kudo says workstation WG wants it bumped to 2.5 GB. as aoife is out sick adam will try and get the f41 blocking page created with the new size (@adamwill:fedora.im, 17:00:38)
    4. ACTION: adamw to get f41 pgm docs created (@adamwill:fedora.im, 17:00:49)
  11. TOPIC:(2305291) GRUB 2.12 generated grub.cfg does not work with GRUB 2.06 (@adamwill:fedora.im, 17:01:15)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2305291 (@adamwill:fedora.im, 17:01:18)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1618 (@adamwill:fedora.im, 17:01:21)
    3. INFO: Accepted Blocker, grub2, NEW (@adamwill:fedora.im, 17:01:23)
    4. INFO: it seems like the shape of this issue is known and there's a workaround for the atomic desktops, but there doesn't seem to be anything in place yet to address it for IoT (@adamwill:fedora.im, 17:06:07)
  12. TOPIC:(2282171) gsk: vulkan renderer causes gtk4 apps to crash on resize operations on Raspberry Pi 4 and 400 (@adamwill:fedora.im, 17:06:52)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2282171 (@adamwill:fedora.im, 17:06:55)
    2. INFO: Accepted Blocker, gtk4, NEW (@adamwill:fedora.im, 17:06:57)
    3. INFO: we are still waiting for the various upstreams here to agree on who needs to fix what to address this (@adamwill:fedora.im, 17:17:25)
    4. ACTION: František Zatloukal to file a new upstream gtk issue clearly explaining the remaining issue, with the stace trace attached (@adamwill:fedora.im, 17:17:43)
    5. ACTION: adamw to alert fesco to the stuck blocker (@adamwill:fedora.im, 17:18:01)
  13. TOPIC:(2283978) Raspberry Pi 4 automatically suspends when idle, claims to support suspend, but can't be woken up (@adamwill:fedora.im, 17:18:15)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2283978 (@adamwill:fedora.im, 17:18:18)
    2. INFO: Accepted Blocker, kernel, NEW (@adamwill:fedora.im, 17:18:20)
    3. INFO: this more or less boils down to 'find a way to disable suspend only on raspberry pis (but not in the kernel because jforbes says that won't fly upstream), or document it and move on'. we had some ideas in the meeting which we can note in the bugzilla (@adamwill:fedora.im, 17:28:00)
    4. INFO: 2309138 is ON_QA so let's assume that's on track (@adamwill:fedora.im, 17:28:21)
  14. TOPIC:(2270430) Raspberry Pi 4: KDE initial setup is broken without nomodeset, KDE desktop won't load with nomodeset (@adamwill:fedora.im, 17:28:32)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2270430 (@adamwill:fedora.im, 17:28:35)
    2. INFO: Accepted Blocker, xorg-x11-server-Xwayland, POST (@adamwill:fedora.im, 17:28:38)
    3. INFO: this is in progress with a patch posted upstream, some possible side effects of the patch are being discussed, we will continue to monitor progress, there is enough time to let it ride for a bit before attempting a build (@adamwill:fedora.im, 17:29:51)
  15. TOPIC:Open floor (@adamwill:fedora.im, 17:30:23)


Meeting ended at 17:32:34 UTC

Action items

  1. adamw to mail arm@ list about reconciling the supported HW lists
  2. adamw to get f41 pgm docs created
  3. František Zatloukal to file a new upstream gtk issue clearly explaining the remaining issue, with the stace trace attached
  4. adamw to alert fesco to the stuck blocker


People present (lines said)

  1. @adamwill:fedora.im (162)
  2. @frantisekz:fedora.im (41)
  3. @conan_kudo:matrix.org (27)
  4. @nielsenb:fedora.im (27)
  5. @zodbot:fedora.im (20)
  6. @pbrobinson:fedora.im (15)
  7. @sgallagh:fedora.im (10)
  8. @geraldosimiao:matrix.org (8)
  9. @nhanlon:beeper.com (7)
  10. @farribeiro:matrix.org (5)
  11. @kparal:matrix.org (4)
  12. @derekenz:fedora.im (3)
  13. @amoloney:fedora.im (3)
  14. @jnsamyak:matrix.org (2)
  15. @meetbot:fedora.im (2)
  16. @humaton:fedora.im (1)
  17. @jannau:fedora.im (1)
  18. @sumantrom:fedora.im (1)


1 Like