BetaBlocker -1

This release criterion isn't intended to cover hardware-specific issues.

I think this must be tested further to assure its really a hardware issue.

@catanzaro this is the case for x86_64, but for ARM it's a little different. For ARM we have a specific list of supported hardware and it's a release blocker if anything on that list doesn't meet the criteria. Raspberry Pi 4 is on the list, and is of course an extremely common platform to run Fedora ARM on (probably the most common platform). Pi 4 not getting to a desktop on the only release-blocking desktop spin for ARM is definitely a blocker, for me.

edit: after a bit of criteria lawyer-ing, I realized we can cite https://fedoraproject.org/wiki/Basic_Release_Criteria#Release-blocking_images_must_boot instead. It's kinda clearer because it's right after the "supported ARM platforms" definition.

BetaBlocker +0

AGREED AcceptedBetaBlocker

Discussed during the 2024-02-19 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Beta)" was made as it violates the following criterion:

"Release-blocking ARM disk images must boot to the initial-setup utility" for the ARM Workstation disk image (which is release-blocking) on the Raspberry PI 4 (which is a "supported ARM platform" as defined right above that criterion).

[0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-19/f40-blocker-review.2024-02-19-17.00.log.txt

The following votes have been closed:

• Accepted BetaBlocker (+0, 0, -1)
  • -1 by catanzaro

Release F40 is no longer tracked by BlockerBugs, closing this ticket.