From Fedora Project Wiki
(Add trackers)
 
(15 intermediate revisions by 2 users not shown)
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/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 -->
<!-- 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 22: Line 18:
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF35]]
<!-- 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 32: Line 27:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
<!--[[Category:SelfContainedChange]]-->
<!-- [[Category:SystemWideChange]] -->
[[Category:SystemWideChange]]


* Targeted release: [[Releases/35 | Fedora Linux 35 ]]  
* Targeted release: [[Releases/35 | Fedora Linux 35 ]]  
Line 43: Line 38:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2635 #2635]
* Tracker bug: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1982397 #1982397]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/714 #714]


== Detailed Description ==
== Detailed Description ==
Line 96: Line 91:


<!-- 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: <!-- REQUIRED FOR SYSTEM WIDE 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 clang12 and llvm12 compatibility packages if they want to rebuild their package and it does not work with LLVM 13 yet.  The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 13 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 clang12 and llvm12 compatibility packages if they want to rebuild their package and it does not work with LLVM 13 yet.  The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 13 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?-->
<!-- 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/issues/10179] <!-- 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 118: Line 112:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
This change should not impact upgradeability.


== How To Test ==
== How To Test ==
Line 136: Line 130:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 
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 13.


== User Experience ==
== User Experience ==
Line 150: Line 144:
-->
-->
Users will benefit from new features and bug-fixes in the latest version of LLVM.
Users will benefit from new features and bug-fixes in the latest version of LLVM.


== Dependencies ==
== Dependencies ==
Line 162: Line 155:


<!-- 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?): If there are major problems with LLVM 13, the compatibility package provide a way for other packages to continue using LLVM 12.
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: Final Freeze
 
* Blocks release? No
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
Beta Freeze.
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 


== Documentation ==
== Documentation ==
Line 175: Line 163:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
Release notes will be added for this change.


== Release Notes ==
== Release Notes ==

Latest revision as of 19:05, 14 July 2021


LLVM 13

Summary

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

Owner

Current status

Detailed Description

All llvm sub-projects in Fedora will be updated to version 13, and there will be a soname version change for the llvm libraries. Compatibility packages clang12 and llvm12 will be added to ensure that packages that currently depend on clang and llvm version 12 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.
    • Request a side-tag.
    • Build llvm12 and clang12 into the side-tag.
    • When the upstream LLVM project releases version 12.0.0-rc1 (Late July 2021), package this and build it into the side tag.
    • Merge side-tag into rawhide prior to the f35 branch date.
    • Continue packaging newer release candidates into rawhide and f35 until the final release is complete (Late September 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 clang12 and llvm12 compatibility packages if they want to rebuild their package and it does not work with LLVM 13 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 13 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.
  • Release engineering: [1]
  • 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 13.

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 12 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 13, the compatibility package provide a way for other packages to continue using LLVM 12.
  • 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 13:

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