Changes/LLVM-14

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

LLVM 14

Summary

Update all llvm sub-projects in Fedora Linux to version 14.

Owner

• Name: Tom Stellard
• Email: <tstellar@redhat.com>

Current status

• Targeted release: Fedora Linux 36
• Last updated: 2021-12-02
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

All llvm sub-projects in Fedora will be updated to version 14, and there will be a soname version change for the llvm libraries. Compatibility packages clang13 and llvm13 will be added to ensure that packages that currently depend on clang and llvm version 13 libraries will continue to work.

Unlike previous releases, we will no longer be packaging release candidate builds in Rawhide or F36. Release candidates are not guaranteed to be ABI compatible with each other, so upgrading from one release candidate to another (or to the final release) requires rebuilding all the clang/LLVM library users and this has become very difficult to coordinate given the increased number of packages using the clang/LLVM libraries.

We do plan to build release candidate versions into a side-tag for testing. We will also create an llvm-14 branch in dist-git, so that we can build the release candidate versions while still being able to fix bugs and make changes to LLVM 13 in the rawhide branch.

Benefit to Fedora

New features and bug fixes provided by the latest version of LLVM.

Scope

• Proposal owners:

• Other developers:

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with Objectives:

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)