(→Scope) |
(Add trackers) |
||
(12 intermediate revisions by 2 users not shown) | |||
Line 53: | Line 53: | ||
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 | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1787374 #1787374] | ||
* Release notes tracker: | * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/425 #425] | ||
== Detailed Description == | == Detailed Description == | ||
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 10. | All llvm sub-projects in Fedora will be updated to version 10, and there will be a soname version change for the llvm libraries. Compatibility packages clang9.0 and llvm9.0 will be added to ensure that packages that currently depend on clang and llvm version 9 libraries will continue to work. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Line 105: | Line 105: | ||
<!-- 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 clang9.0 and llvm9.0 if they want to rebuild their package and it does not work with | ** Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang9.0 and llvm9.0 compatibility packages if they want to rebuild their package and it does not work with LLVM 10 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 10 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/ | * Release engineering: [https://pagure.io/releng/issues/9099] (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 157: | Line 157: | ||
--> | --> | ||
Users will benefit from new features and bug-fixes in the latest version of LLVM. | |||
== Dependencies == | == Dependencies == | ||
Line 166: | Line 164: | ||
<!-- 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. | |||
== 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 | * Contingency mechanism: (What to do? Who will do it?) If there are major problems with LLVM 10, the compatibility package provide a way for other packages to continue using LLVM 9. In the worst case, we could always revert LLVM back to LLVM 9, 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. --> | ||
* Contingency deadline: | * Contingency deadline: Beta Freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Line 208: | Line 190: | ||
--> | --> | ||
LLVM sub-projects in Fedora have been updated to version 10: | |||
* llvm | |||
* clang | |||
* lld | |||
* lldb | |||
* compiler-rt | |||
* libomp | |||
* llvm-test-suite | |||
* libcxx | |||
* libcxxabi | |||
* python-lit | |||
[[Category: | [[Category:ChangeAcceptedF32]] | ||
<!-- 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 --> |
Latest revision as of 15:47, 2 January 2020
LLVM 10
Summary
Update all llvm sub-projects in Fedora to version 10.
Owner
- Name: Tom Stellard
- Email: <tstellar@redhat.com>
Current status
- Targeted release: Fedora 32
- Last updated: 2020-01-02
- Tracker bug: #1787374
- Release notes tracker: #425
Detailed Description
All llvm sub-projects in Fedora will be updated to version 10, and there will be a soname version change for the llvm libraries. Compatibility packages clang9.0 and llvm9.0 will be added to ensure that packages that currently depend on clang and llvm version 9 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 f32-llvm side-tag from Release Engineering.
- Build llvm9.0 and clang9.0 into the side-tag.
- When the upstream LLVM project releases version 10.0.0-rc1 (2020-1-15), package this and build it into the side tag.
- Merge side-tag into rawhide prior to the f32 branch date.
- Continue packaging newer release candidates into rawhide and f32 until the final release is complete (~2020-2-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 clang9.0 and llvm9.0 compatibility packages if they want to rebuild their package and it does not work with LLVM 10 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 10 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 10.
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 9 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 10, the compatibility package provide a way for other packages to continue using LLVM 9. In the worst case, we could always revert LLVM back to LLVM 9, 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 10:
- llvm
- clang
- lld
- lldb
- compiler-rt
- libomp
- llvm-test-suite
- libcxx
- libcxxabi
- python-lit