From Fedora Project Wiki
(Add trackers)
 
(8 intermediate revisions by 2 users not shown)
Line 44: Line 44:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF34]]
[[Category:SystemWideChange]]
[[Category:SystemWideChange]]
* Targeted release: [[Releases/34 | Fedora 34 ]]  
* Targeted release: [[Releases/34 | Fedora 34 ]]  
Line 55: Line 55:
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
-->
-->
* FESCo issue: []
* FESCo issue: [https://pagure.io/fesco/issue/2526 #2526]
* Tracker bug: []
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1913432 #1913432]
* Release notes tracker: []
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/626 #626]


== Detailed Description ==
== Detailed Description ==
Line 63: Line 63:
<!-- 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 12, and there will be a soname version change for the llvm libraries. Compatibility packages clang11 and llvm11 will be added to ensure that packages that currently depend on clang and llvm version 10 libraries will continue to work.
All llvm sub-projects in Fedora will be updated to version 12, and there will be a soname version change for the llvm libraries. Compatibility packages clang11 and llvm11 will be added to ensure that packages that currently depend on clang and llvm version 11 libraries will continue to work.


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 112: Line 112:
  <!-- 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: [] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issue/9902] (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 167: 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 10 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 11 will need to update their spec file on their first rebuild after this change.


== Contingency Plan ==
== 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.  -->
<!-- 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?)  If there are major problems with LLVM 12, 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 11, but this would only happen if their were an unprecedented amount of problems.  
* Contingency mechanism: (What to do?  Who will do it?)  If there are major problems with LLVM 12, the compatibility package provide a way for other packages to continue using LLVM 11.  In the worst case, we could always revert LLVM back to LLVM 11, but this would only happen if their were an unprecedented amount of problems.  


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

Latest revision as of 18:43, 6 January 2021


LLVM 12

Summary

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

Owner

Current status

Detailed Description

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

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 side-tag.
    • Build llvm11 and clang11 into the side-tag.
    • When the upstream LLVM project releases version 12.0.0-rc1 (Jan 2021), package this and build it into the side tag.
    • Merge side-tag into rawhide prior to the f34 branch date.
    • Continue packaging newer release candidates into rawhide and f34 until the final release is complete (~March 2021)
  • Other developers:
    • Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang11 and llvm11 compatibility packages if they want to rebuild their package and it does not work with LLVM 12 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 12 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 12.

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 11 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 12, the compatibility package provide a way for other packages to continue using LLVM 11. In the worst case, we could always revert LLVM back to LLVM 11, 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 12:

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