Fedora is currently shipping version 2020.3 (released July 10, 2020) of the Thread Building Blocks library. The current upstream version is 2021.8 (released December 22, 2022). The Fedora community has expressed interest in moving the TBB package to track a more modern version of the upstream.
Owners, do not implement this work until the FESCo vote has explicitly ended. The Fedora Program Manager will create a tracking bug in Bugzilla for this Change, which is your indication to proceed. See the FESCo ticket policy and the Changes policy for more information.
REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the devel list thread linked above.
+1
I am a bit concerned about the large cluster of packages identified by Jerry James that would need to move to the current TBB all at once (and which are not all maintained upstream). These include some rather important packages. It seems like these will eventually need to move off the compat package, and it’s not clear who will be able to do the work to make that happen.
Having said that, I still think that it’s time to go ahead and move forward where we can, and that the implications and details of introducing a compat package have been adequately thought through in the original tracking issue. Thank you for doing this work.
On Tue, Feb 28, 2023 at 5:45=E2=80=AFAM Benjamin Beasley pagure@pagure.io= wrote:
music added a new comment to an issue you are following: `` I am a bit concerned about the large cluster of packages identified by Jerry James th= at would need to move to the current TBB all at once (and which are not all maintained upstream). These include some rather important packages. It seems like these will eventually need to move off the compat package, a= nd it=E2=80=99s not clear who will be able to do the work to make that happe= n. This is a mess of the upstream's making really. TBB had maintained ABI stability for over a decade and was included in RHEL's ACG level 0. We had to remove it from ACG0 a couple of years ago because it was not going to be possible to continue making long term stability guarantees about newer versions of TBB. I know this stability expectation is less of a concern for Fedora, and I anticipate more collateral breakage with future updates to TBB for those packages that are not using the compat version, and it is entirely possible that the compat package will need to be carried forward indefinitely. Having said that, I still think that it=E2=80=99s time to go ahead and mo= ve forward where we can, and that the implications and details of introducin= g a compat package have been adequately thought through in the original tracking issue. Thank you for doing this work. +1 `` To reply, visit the link below or just reply to this email https://pagure.io/fesco/issue/2959
music added a new comment to an issue you are following: `` I am a bit concerned about the large cluster of packages identified by Jerry James th= at would need to move to the current TBB all at once (and which are not all maintained upstream). These include some rather important packages. It seems like these will eventually need to move off the compat package, a= nd it=E2=80=99s not clear who will be able to do the work to make that happe= n.
This is a mess of the upstream's making really. TBB had maintained ABI stability for over a decade and was included in RHEL's ACG level 0. We had to remove it from ACG0 a couple of years ago because it was not going to be possible to continue making long term stability guarantees about newer versions of TBB. I know this stability expectation is less of a concern for Fedora, and I anticipate more collateral breakage with future updates to TBB for those packages that are not using the compat version, and it is entirely possible that the compat package will need to be carried forward indefinitely.
Having said that, I still think that it=E2=80=99s time to go ahead and mo= ve forward where we can, and that the implications and details of introducin= g a compat package have been adequately thought through in the original tracking issue. Thank you for doing this work.
+1 ``
To reply, visit the link below or just reply to this email https://pagure.io/fesco/issue/2959
On Tue, Feb 28, 2023 at 5:45=E2=80=AFAM Benjamin Beasley pagure@pagure.io= wrote: music added a new comment to an issue you are following: `` I am a bit concerned about the large cluster of packages identified by Jerry James th= at would need to move to the current TBB all at once (and which are not all maintained upstream). These include some rather important packages. It seems like these will eventually need to move off the compat package, a= nd it=E2=80=99s not clear who will be able to do the work to make that happe= n. This is a mess of the upstream's making really. TBB had maintained ABI stability for over a decade and was included in RHEL's ACG level 0. We had to remove it from ACG0 a couple of years ago because it was not going to be possible to continue making long term stability guarantees about newer versions of TBB. I know this stability expectation is less of a concern for Fedora, and I anticipate more collateral breakage with future updates to TBB for those packages that are not using the compat version, and it is entirely possible that the compat package will need to be carried forward indefinitely. Having said that, I still think that it=E2=80=99s time to go ahead and mo= ve forward where we can, and that the implications and details of introducin= g a compat package have been adequately thought through in the original tracking issue. Thank you for doing this work. +1 `` To reply, visit the link below or just reply to this email https://pagure.io/fesco/issue/2959
Mail made a bit of a mess of my reply to @music -
After a week, the vote is APPROVED (+5,0,-0)
Metadata Update from @bcotton: - Issue tagged with: pending announcement
Announced.
Metadata Update from @zbyszek: - Issue untagged with: pending announcement - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Note: this Change has now been dropped.
Login to comment on this ticket.