m (remove the proposal banner) |
|||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= LLVM 15 <!-- The name of your change proposal --> = | = LLVM 15 <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
Line 26: | Line 20: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF37]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Line 44: | Line 38: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* FESCo issue: | * [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EAYAO5E5IWTWZQKM26RHOOYUGSX5PSHV/ devel thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/2806 #2806] | ||
* Release notes tracker: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2100620 #2100620] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/849 #849] | |||
== Detailed Description == | == Detailed Description == | ||
Line 115: | Line 110: | ||
== How To Test == | == How To Test == | ||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
Line 129: | Line 123: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
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. | |||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Latest revision as of 16:06, 1 July 2022
LLVM 15
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-07-01
- devel thread
- FESCo issue: #2806
- Tracker bug: #2100620
- Release notes tracker: #849
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
Release notes will be added for this change.
Release Notes
LLVM sub-projects in Fedora have been updated to version 15:
llvm clang lld lldb compiler-rt libomp llvm-test-suite libcxx libcxxabi python-lit flang mlir polly libclc llvm-unwind