From Fedora Project Wiki
< Changes
| Line 152: | Line 152: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) | * Contingency mechanism: (What to do? Who will do it?) Contingency mechanism: (What to do? Who will do it?): If there are major problems with LLVM 15, the compatibility package provide a way for other packages to continue using LLVM 14. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: Final Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Documentation == | == Documentation == | ||
Revision as of 06:18, 1 June 2022
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.
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.
For details on how to fill out this form, see the documentation.
LLVM 15
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Update all llvm sub-projects in Fedora Linux to version 15.
Owner
- Name: Tom Stellard
- Email: <tstellar@redhat.com>
Current status
- Targeted release: Fedora Linux 37
- Last updated: 2022-06-01
- 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 15, and there will be a soname version change for the llvm libraries. Compatibility packages clang14 and llvm14 will be added to ensure that packages that currently depend on clang and llvm version 14 libraries will continue to work.
Feedback
Benefit to Fedora
New features and bug fixes provided by the latest version of LLVM.
Scope
- Proposal owners:
- Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.
- Build release candidates into @fedora-llvm-team/llvm15 COPR.
- Build final release (Sep 2022) into Rawhide and F37 branches.
- Other developers:
- Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang14 and llvm14 compatibility packages if they want to rebuild their package and it does not work with LLVM 15 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 15 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.
- Release engineering: #10820
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
This change should not impact upgradeability.
How To Test
The CI tests for the llvm sub-packages in Fedora will be used to catch regressions that might be potentially introduced by the update to LLVM 15.
User Experience
Dependencies
This change can be made without updating any other packages. However, as mention before, packages that need to use LLVM 14 will need to update their spec file on their first rebuild after this change.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) Contingency mechanism: (What to do? Who will do it?): If there are major problems with LLVM 15, the compatibility package provide a way for other packages to continue using LLVM 14.
- Contingency deadline: Final Freeze
- Blocks release? No
Documentation
N/A (not a System Wide Change)