Revision as of 00:37, 26 June 2021

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.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Change Proposal Name

LLVM 13

Summary

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

Owner

Name: Tom Stellard
Email: <tstellar@redhat.com>
Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>

Current status

Targeted release: Fedora Linux 35
Last updated: 2021-06-26
FESCo issue: <will be assigned by the Wrangler>
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 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 f34 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: #Releng issue number

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

How To Test

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 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: N/A (not a System Wide Change)

Beta Freeze.

Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide 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

@@ Line 6: / Line 6: @@
 = Change Proposal Name =
+LLVM 13
 <!-- The name of your change proposal -->
 == Summary ==
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
+Update all llvm sub-projects in Fedora to version 13.
 == Owner ==
@@ Line 16: / Line 19: @@
 This should link to your home wiki page so we know who you are.
 -->
-* Name: [[User:FASAcountName| Your Name]]
+* Name: [[User:tstellar| Tom Stellard]]
+* Email: <tstellar@redhat.com>
 <!-- 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. -->
 * Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
@@ Line 35: / Line 39: @@
 <!-- [[Category:SystemWideChange]] -->
-* Targeted release: [[Releases/<number> | Fedora Linux <number> ]]
+* Targeted release: [[Releases/35 | Fedora Linux 35 ]]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 49: / Line 53: @@
 == Detailed Description ==
 <!-- 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 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 ==
@@ Line 81: / Line 88: @@
       https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+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 f34 branch date.
+** Continue packaging newer release candidates into rawhide and f35 until the final release is complete (Late September 2021)
 <!-- 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 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?-->
@@ Line 137: / Line 154: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+Users will benefit from new features and bug-fixes in the latest version of LLVM.
 == Dependencies ==
@@ Line 143: / Line 162: @@
 <!-- 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 12 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?):
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+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: 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 -->
@@ Line 166: / Line 188: @@
 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 13:
+* llvm
+* clang
+* lld
+* lldb
+* compiler-rt
+* libomp
+* llvm-test-suite
+* libcxx
+* libcxxabi
+* python-lit
+* flang
+* mlir
+* polly
+* libclc

Search

Changes/LLVM-13: Difference between revisions