Changes/F39ModernizeTBB

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.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

Modernize Thread Building Blocks

This is a proposed Change for Fedora Linux.
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.

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.

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.

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:

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)