Latest revision as of 17:00, 13 January 2022

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: 2022-01-13
devel thread
FESCo issue: #2726
Tracker bug: #2040428
Release notes tracker: #786

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. This has become very difficult to coordinate given the increased number of packages using the clang/LLVM libraries, so we decided to only package the final release.

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.

Note: we are still discussing with Release Engineering if a branch + side-tag will be possible #10414. If it's not possible, we will use COPR instead.

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.
- Request an llvm-14 branch in dist-git for each llvm sub-project.
- Request a side-tag.
- Build llvm13 and clang13 compat packages into the side-tag.
- When upstream LLVM project releases version 14.0.0-rc1 (Late January 2021), package this using the llvm-14 branches and build it into the side-tag.
  - Repeat process for each release candidate.
- When upstream LLVM project releases version 14.0.0-final (March 2021), package this using the rawhide and f36 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 clang13 and llvm13 compatibility packages if they want to rebuild their package and it does not work with LLVM 14 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 14 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.

Release engineering: #10414

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 14.

User Experience

Users will benefit from new features and bug-fixes in the latest version of LLVM.

Dependencies

This change can be made without updating any other packages. However, as mention before, packages that need to use LLVM 13 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?): If there are major problems with LLVM 14, the compatibility package provide a way for other packages to continue using LLVM 13.

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 14:

llvm
clang
lld
lldb
compiler-rt
libomp
llvm-test-suite
libcxx
libcxxabi
python-lit
flang
mlir
polly
libclc
llvm-unwind

@@ Line 1: / Line 1: @@
-{{admon/important | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+<!--{{admon/important | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 {{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
+-->
 <!-- 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 -->
@@ Line 26: / Line 27: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF36]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 44: / Line 45: @@
 ON_QA -> change is fully code complete
 -->
-* FESCo issue: <will be assigned by the Wrangler>
+* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/W7KG4VKBUL5IIOYPSWNTSGKWSSII253T/ devel thread]
-* Tracker bug: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/2726 #2726]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2040428 #2040428]
+* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/786 #786]
 == Detailed Description ==
@@ Line 52: / Line 54: @@
 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.
+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.  This has become very difficult to coordinate given the increased number of packages using the clang/LLVM libraries, so we decided to only package the final release.
+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.
-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.
+'''Note: we are still discussing with Release Engineering if a branch + side-tag will be possible [https://pagure.io/releng/issue/10414 #10414].  If it's not possible, we will use COPR instead.'''
 == Feedback ==
@@ Line 91: / Line 95: @@
 == Scope ==
 * Proposal owners:
-  * Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.
+** Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.
-  * Request an llvm-14 branch in dist-git for each llvm sub-project.
+** Request an llvm-14 branch in dist-git for each llvm sub-project.
-  * Request a side-tag.
+** Request a side-tag.
-  * Build llvm13 and clang13 compat packages into the side-tag.
+** Build llvm13 and clang13 compat packages into the side-tag.
-  * When upstream LLVM project releases version 14.0.0-rc1 (Late January 2021), package this using the llvm-14 branches and build it into the side-tag.
+** When upstream LLVM project releases version 14.0.0-rc1 (Late January 2021), package this using the llvm-14 branches and build it into the side-tag.
-    * Repeat process for each release candidate.
+*** Repeat process for each release candidate.
-  * When upstream LLVM project releases version 14.0.0-final (March 2021), package this using the rawhide and f36 branches.
+** When upstream LLVM project releases version 14.0.0-final (March 2021), package this using the rawhide and f36 branches.
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-  * Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang13 and llvm13 compatibility packages if they want to rebuild their package and it does not work with LLVM 14 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 14 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.
+** Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang13 and llvm13 compatibility packages if they want to rebuild their package and it does not work with LLVM 14 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 14 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: [https://pagure.io/releng/issue/10414 #10414] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
@@ Line 123: / Line 127: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+This change should not impact upgradeability.
 == How To Test ==
@@ Line 145: / Line 149: @@
 == User Experience ==
+Users will benefit from new features and bug-fixes in the latest version of LLVM.
 <!-- If this change proposal is noticeable by users, how will their experiences change as a result?
@@ Line 160: / Line 165: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+This change can be made without updating any other packages. However, as mention before, packages that need to use LLVM 13 will need to update their spec file on their first rebuild after this change.
 == Contingency Plan ==
 <!-- 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?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: (What to do?  Who will do it?): If there are major problems with LLVM 14, the compatibility package provide a way for other packages to continue using LLVM 13.
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: Final Freeze
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? No
 == Documentation ==
@@ Line 176: / Line 181: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+Release notes will be added for this change.
 == Release Notes ==
@@ Line 184: / Line 189: @@
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
+LLVM sub-projects in Fedora have been updated to version 14:
+* llvm
+* clang
+* lld
+* lldb
+* compiler-rt
+* libomp
+* llvm-test-suite
+* libcxx
+* libcxxabi
+* python-lit
+* flang
+* mlir
+* polly
+* libclc
+* llvm-unwind

Search

Changes/LLVM-14: Difference between revisions