< Changes
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Modernize Thread Building Blocks = | = Modernize Thread Building Blocks for Fedora 39 = | ||
{{Change_Proposal_Banner}} | {{Change_Proposal_Banner}} | ||
| Line 8: | Line 8: | ||
to track a more modern version of the upstream. | to track a more modern version of the upstream. | ||
== Owner == | == Owner == | ||
* Name: [[User:trodgers| Thomas Rodgers]] | * Name: [[User:trodgers| Thomas Rodgers]] | ||
| Line 45: | Line 43: | ||
Fedora packaging for TBB. The situation is further complicated by not all dependent packages having | Fedora packaging for TBB. The situation is further complicated by not all dependent packages having | ||
been updated to track the latest upstream changes, as detailed in this [https://bugzilla.redhat.com/show_bug.cgi?id=2036372#c1 comment] on the tracking issue. | been updated to track the latest upstream changes, as detailed in this [https://bugzilla.redhat.com/show_bug.cgi?id=2036372#c1 comment] on the tracking issue. | ||
This proposal is part of a pair of proposals that aim to provide a way to modernize the TBB packging for | |||
Fedora while providing stability for those packages which are dependent on the older TBB library version. | |||
== Feedback == | == Feedback == | ||
<!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. --> | ||
Revision as of 23:50, 5 February 2023
Modernize Thread Building Blocks for Fedora 39
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Fedora is currently shipping version 2020.3 (released July 10, 2020) of the Thread Building Blocks library. The current upstream version is 2021.7 (released October 28, 2022). The Fedora community has expressed interest in moving the TBB package to track a more modern version of the upstream.
Owner
- Name: Thomas Rodgers
- Email: trodgers@redhat.com
Current status
- Targeted release: Fedora 39
- Last updated: 2023-02-05
- 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
Fedora has shipped with version 2020.3 of the Thread Building Blocks library since Fedora 33. The upstream project made a decision to break backward compatibility after this release. As packages have moved to match the upstream's changes it has become more difficult to continue to defer updating the Fedora packaging for TBB. The situation is further complicated by not all dependent packages having been updated to track the latest upstream changes, as detailed in this comment on the tracking issue.
This proposal is part of a pair of proposals that aim to provide a way to modernize the TBB packging for Fedora while providing stability for those packages which are dependent on the older TBB library version.
Feedback
Benefit to Fedora
Scope
- Proposal owners:
- Other developers:
- 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
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)