I'm a little concerned about landing this a week-ish before Go/No-Go. I'd like to be +1, so talk me into it. :-)

@tstellar may chime in and talk you a bit more :) , from my PoV, this will land in F36 anyway and I'd rather see fallout now during the freeze than as a 0day update.

The LLVM 14 bodhi update is still not complete. We need to add the lld13-13.0.1-1.fc36 package and are currently blocked from doing so by this issue: https://pagure.io/fedora-infrastructure/issue/10633

Assuming the update were complete, what I would say is:

We have been testing the LLVM14 builds for almost a month and we have a large number of CI tests, so I feel good about the stability of those packages. We provide compatibility packages for users of the previous version of the LLVM libraries, so this update should not impact any of the current LLVM13 library users.

The risk to pushing now is that we may introduce some 'Fail To Install' errors in packages that have an explicit dependency on LLVM13 rather than relaying on the auto-generated library dependencies. We have caught and fixed one such package already in the update. Do we have a CI test that checks for these?

I'd rather see fallout now during the freeze than as a 0day update.

This makes sense to me, although I don't necessarily feel good about it. :-)

FinalFE +1

FinalFE +1

from me obviously :)

FinalFE +1

when @bcotton says so :D

AGREED AcceptedFinalFE This is a bigger F36 approved change that missed Final Freeze by a bit. It's been baking in updates-testing for a while and we haven't seen a significant fallout from it.

The following votes have been closed:

• Accepted FinalFreezeException (+3, 0, -0)
  • +1 by bcotton, frantisekz, lruzicka

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