2024-02-12 @ 17:00 UTC - Fedora 40 Blocker Review Meeting

Project Discussion
, , ,
1

Hi folks! Fedora 40 branches this coming week, and we have some blockers to check in on, so it seems like a good time for a blocker review meeting. We are still on standard time in places that use daylight savings, so the meeting is at 17:00 UTC.

The meeting will be on Matrix, as we’re trying to move to more modern systems and the meeting bot is working on Matrix now. 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!

2 Likes
2

Added engineering, release-engineering-team, workstation-wg

3

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

Meeting started by @adamwill:fedora.im at 17:05:09 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 17:05:13)
  2. TOPIC:Introduction (@adamwill:fedora.im, 17:08:57)
    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, 17:09:08)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 17:09:11)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 17:09:14)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 17:09:16)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 17:09:19)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 17:09:22)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 17:09:26)
    8. LINK: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria (@adamwill:fedora.im, 17:09:29)
    9. LINK: https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria (@adamwill:fedora.im, 17:09:31)
    10. INFO: for Beta, we have: (@adamwill:fedora.im, 17:09:49)
    11. INFO: 5 Proposed Blockers (@adamwill:fedora.im, 17:09:52)
    12. INFO: 2 Accepted Blockers (@adamwill:fedora.im, 17:09:55)
    13. INFO: 1 Accepted Previous Release Blockers (@adamwill:fedora.im, 17:09:58)
    14. INFO: 6 Accepted Freeze Exceptions (@adamwill:fedora.im, 17:10:01)
    15. INFO: for Final, we have: (@adamwill:fedora.im, 17:10:04)
    16. INFO: 3 Proposed Blockers (@adamwill:fedora.im, 17:10:13)
    17. INFO: coremodule will be the secretary (@adamwill:fedora.im, 17:12:59)
  3. TOPIC:Proposed Beta blockers (@adamwill:fedora.im, 17:13:58)
  4. TOPIC:(2263871) Creating a 1 MB partition creates a 999 MB partition instead (@adamwill:fedora.im, 17:14:00)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2263871 (@adamwill:fedora.im, 17:14:03)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1457 (@adamwill:fedora.im, 17:14:06)
    3. INFO: Proposed Blocker, cockpit, POST (@adamwill:fedora.im, 17:14:09)
    4. INFO: Ticket vote: BetaBlocker (+1,0,-0) (+nielsenb) (@adamwill:fedora.im, 17:14:13)
    5. AGREED: 2263871 - AcceptedBlocker (Beta) - this is accepted as a violation of "When using both the installer-native and the blivet-gui-based custom partitioning flow, the installer must be able to: Assign sizes to newly-created storage volumes and containers". technically it can do that, but not in a way that makes any sense to a user. We are considering cockpit to be the 'installer-native' custom partitioning flow for current Workstation live images (@adamwill:fedora.im, 17:26:39)
    6. INFO: 2243872 has +4 votes in the ticket so it should be accepted already, skipping (I will mark it accepted) (@adamwill:fedora.im, 17:27:12)
  5. TOPIC:(2259050) Workstation Live boots to corrupted desktop display (@adamwill:fedora.im, 17:27:20)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2259050 (@adamwill:fedora.im, 17:27:23)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1455 (@adamwill:fedora.im, 17:27:27)
    3. INFO: Proposed Blocker, mutter, NEW (@adamwill:fedora.im, 17:27:30)
    4. INFO: Ticket vote: BetaBlocker (+0,0,-2) (-tablepc, -nielsenb) (@adamwill:fedora.im, 17:27:32)
    5. AGREED: 2259050 - punt (delay decision) - there are strong indications that this is fixed by a recent kernel, mesa and/or mutter update, so we are punting in the expectation it will be closed as fixed with confirmation from lbrabec soon. If not, we will reconsider it next time (@adamwill:fedora.im, 17:40:05)
  6. TOPIC:(2236356) the software raid disk becomes unusable after click "Rescan" twice (@adamwill:fedora.im, 17:40:27)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2236356 (@adamwill:fedora.im, 17:40:30)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1321 (@adamwill:fedora.im, 17:40:34)
    3. INFO: Proposed Blocker, python-blivet, ASSIGNED (@adamwill:fedora.im, 17:40:37)
    4. INFO: Ticket vote: BetaBlocker (+2,0,-0) (+nielsenb, +geraldosimiao) (@adamwill:fedora.im, 17:40:39)
    5. AGREED: 2236356 - punt (delay decision) - with webui currently using cockpit, it would be helpful to clarify for sure what exactly the status of this issue is with webui/cockpit, webui/blivet and the current ui (@adamwill:fedora.im, 17:56:43)
    6. INFO: 2259264 had +4 in ticket votes, I have marked it as accepted (@adamwill:fedora.im, 17:56:58)
  7. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 18:05:10)
  8. TOPIC:(2247872) Don't write /etc/lvm/devices/system.devices when not doing an end-user install (@adamwill:fedora.im, 18:08:03)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2247872 (@adamwill:fedora.im, 18:08:07)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1438 (@adamwill:fedora.im, 18:08:10)
    3. INFO: Proposed Blocker, anaconda, POST (@adamwill:fedora.im, 18:08:13)
    4. INFO: Ticket vote: FinalBlocker (+0,0,-1) (-nielsenb) (@adamwill:fedora.im, 18:08:15)
    5. AGREED: 2247872 - punt (delay decision) - pboy is working through the plan and the implications here, we will delay the decision for a bit so we have a clearer picture (@adamwill:fedora.im, 18:19:51)
  9. TOPIC:(2245371) [x86 MacBook Pro] iso stuck at "Booting a command list" (@adamwill:fedora.im, 18:20:06)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2245371 (@adamwill:fedora.im, 18:20:10)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1418 (@adamwill:fedora.im, 18:20:14)
    3. INFO: Proposed Blocker, grub2, NEW (@adamwill:fedora.im, 18:20:16)
    4. INFO: Ticket vote: FinalBlocker (+2,0,-0) (+osalbahr, +nielsenb) (@adamwill:fedora.im, 18:20:19)
    5. AGREED: 2245371 - punt (delay decision) - it seems this may be resolved already, we will delay the decision while we wait for confirmation from the reporter (@adamwill:fedora.im, 18:35:22)
  10. TOPIC:(2248071) systemd-oomd doesn't kick in on high memory pressure, leading to system lockup (@adamwill:fedora.im, 18:35:28)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2248071 (@adamwill:fedora.im, 18:35:32)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1454 (@adamwill:fedora.im, 18:35:33)
    3. INFO: Proposed Blocker, systemd, NEW (@adamwill:fedora.im, 18:35:35)
    4. INFO: Ticket vote: FinalBlocker (+0,0,-1) (-nielsenb) (@adamwill:fedora.im, 18:35:38)
    5. AGREED: 2248071 - punt (delay decision) - we agreed this bug could do with further testing for a more complete understanding of whether systemd-oomd really isn't working at all, or is not kicking in in certain circumstances, or what. I will post a request for testing (@adamwill:fedora.im, 19:36:01)


Meeting ended at 19:36:14 UTC

Action items

  1. (none)


People present (lines said)

  1. @adamwill:fedora.im (131)
  2. @nielsenb:fedora.im (34)
  3. @conan_kudo:matrix.org (31)
  4. @tablepc:matrix.org (18)
  5. @kparal:matrix.org (13)
  6. @frantisekz:fedora.im (11)
  7. @sgallagh:fedora.im (9)
  8. @zodbot:fedora.im (6)
  9. @pboy:fedora.im (6)
  10. @salimma:fedora.im (4)
  11. @coremodule:fedora.im (2)
  12. @meetbot:fedora.im (2)
  13. @gui1ty:fedora.im (1)
  14. @jkonecny:fedora.im (1)


1 Like