#1911 [Changes Tracking] LLVM 21 | rhbz#2383273
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2383273 **
Information from BlockerBugs App:
2383273

Current vote summary

Commented but haven't voted yet: tstellar

The votes have been last counted at 2025-09-10 15:14 UTC and the last processed comment was #comment-985372

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


Well, since the owner planned on this and fesco voted ok for the change, I think this is an automatic FE.
Here's the text from the change proposal: Our plan is to push 21.1.0 into Fedora 43 during the Beta Freeze with a Beta Freeze exception. We are not planning to push earlier release candidates into rawhide because the library ABI is not stabilized until the final 21.1.0 release.

BetaFE +1

Just think that the right component for this is not the "bug traking ticket" or? This is the bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2c0b8bd637

BetaFE +1

I guess:
BetaFE +1
reluctantly.

This is how the change detailed landing LLVM 21, and it would be nice to testing to start sooner rather than later.

BetaFE +1

Approved by FESCo:

BetaFE +1
AGREED AcceptedBetaFreezeException

The following votes have been closed:

Is there any action I need to take to push the update to stable?

No, we'll handle that, thanks. But we really need karma for that, so finding people who can test it at least in some basic sense and give karma would help a lot.

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

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

Metadata