From Fedora Project Wiki
No edit summary
Line 60: Line 60:
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->


All llvm sub-projects in Fedora will be updated to version 11, and there will be a soname version change for the llvm libraries. Compatibility packages clang10.0 and llvm10.0 will be added to ensure that packages that currently depend on clang and llvm version 9 libraries will continue to work.
All llvm sub-projects in Fedora will be updated to version 11, and there will be a soname version change for the llvm libraries. Compatibility packages clang10 and llvm10 will be added to ensure that packages that currently depend on clang and llvm version 10 libraries will continue to work.
 
Also, changing in this update is the compatibility package naming.  The .0 will be dropped from the package name, so the compatibility packages will be called llvm10 and clang10 instead of llvm10.0 and clang10.0.
 


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 98: Line 101:
** 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 a f33-llvm side-tag from Release Engineering.
** Request a f33-llvm side-tag from Release Engineering.
** Build llvm10.0 and clang10..0 into the side-tag.
** Build llvm10 and clang10 into the side-tag.
** When the upstream LLVM project releases version 11.0.0-rc1 (2020-7-15), package this and build it into the side tag.
** When the upstream LLVM project releases version 11.0.0-rc1 (2020-7-15), package this and build it into the side tag.
** Merge side-tag into rawhide prior to the f33 branch date.
** Merge side-tag into rawhide prior to the f33 branch date.
Line 105: Line 108:
<!-- 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?-->
<!-- 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:  
* Other developers:  
** Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang10.0 and llvm10.0 compatibility packages if they want to rebuild their package and it does not work with LLVM 11 yet.  The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 11 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 clang10 and llvm10 compatibility packages if they want to rebuild their package and it does not work with LLVM 11 yet.  The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 11 is added to Fedora.  The compatibility packages will ensure that already built packages continue to work.


  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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?-->
<!-- 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/9099] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issues/] (a check of an impact with Release Engineering is needed) <!-- 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.  
<!-- 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 -->
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 164: Line 167:
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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 9 will need to update their spec file on their first rebuild after this change.
This change can be made without updating any other packages.  However, as mention before, packages that need to use LLVM 10 will need to update their spec file on their first rebuild after this change.


== Contingency Plan ==
== Contingency Plan ==

Revision as of 16:54, 17 June 2020


LLVM 11

Summary

Update all llvm sub-projects in Fedora to version 11.

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-06-17
  • 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 11, and there will be a soname version change for the llvm libraries. Compatibility packages clang10 and llvm10 will be added to ensure that packages that currently depend on clang and llvm version 10 libraries will continue to work.

Also, changing in this update is the compatibility package naming. The .0 will be dropped from the package name, so the compatibility packages will be called llvm10 and clang10 instead of llvm10.0 and clang10.0.


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 a f33-llvm side-tag from Release Engineering.
    • Build llvm10 and clang10 into the side-tag.
    • When the upstream LLVM project releases version 11.0.0-rc1 (2020-7-15), package this and build it into the side tag.
    • Merge side-tag into rawhide prior to the f33 branch date.
    • Continue packaging newer release candidates into rawhide and f33 until the final release is complete (~2020-8-26)
  • Other developers:
    • Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang10 and llvm10 compatibility packages if they want to rebuild their package and it does not work with LLVM 11 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 11 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.
  • Release engineering: [1] (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: No policies or guidelines will need to be updated as a result of this change.
  • Trademark approval: N/A (not needed for this Change)

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

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 10 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 11, the compatibility package provide a way for other packages to continue using LLVM 10. In the worst case, we could always revert LLVM back to LLVM 10, but this would only happen if their were an unprecedented amount of problems.
  • Contingency deadline: Beta Freeze
  • Blocks release? No
  • Blocks product? None

Documentation

Release notes will be added for this change.

Release Notes

LLVM sub-projects in Fedora have been updated to version 11:

  • llvm
  • clang
  • lld
  • lldb
  • compiler-rt
  • libomp
  • llvm-test-suite
  • libcxx
  • libcxxabi
  • python-lit
Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/LLVM-11&oldid=579553"