Without a clearer justification, I'm:
BetaFE -1
I understand this is needed for LLVM 22, but I don't see any explanation why we'd need LLVM 22 in Beta.

I'm not sure why this is being phrased only respective to LLVM 22 -- which is approved for F44 with the knowledge that will come last -- where getting broader testing for an updated Vulkan stack in general seems prudent for Beta, particularly if we know its a requirement for LLVM 22 regardless of when that lands. Not sure if that fits within the usual critera for a BetaFE though.

... I don't see any explanation why we'd need LLVM 22 in Beta.

LLVM 22.1.0 got tagged Feb. 24th. Upstream managed to tag it without any delays.
The Beta phase for Fedora 44 started on Feb. 17th.
The only way to distribute LLVM 22 in Fedora 44 was by asking for a Beta Freeze exception.
This was explained in the change proposal: https://fedoraproject.org/wiki/Changes/LLVM-22#Planned_Schedule

In order to minimize the impact on QA, we've been testing RC releases in our Copr repository: https://copr.fedorainfracloud.org/coprs/g/fedora-llvm-team/llvm22/builds/

If you have any other questions, please let me know.

This appears to be required as per the approved change.

BetaFE +1

Discussed on the Fedora Blocker Review Meeting on March, 2nd 2026 with the resolution.

AGREED RejectedBetaFE

See https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2026-03-02/f44-blocker-review.2026-03-02-17.00.log.txt

The following votes have been closed:

• Rejected BetaFreezeException (+1, 0, -1)
  • +1 by nielsenb
  • -1 by adamwill