Added abi table to VERSIONING.md

[vossmjp]

Description

Added a table to VERSIONING.md to track abi changes by release.

Fixes # - issue number(s) if exists

Type of change

Choose one or multiple, leave empty if none of the other choices apply

Add a respective label(s) to PR if you have permissions

• bug fix - change that fixes an issue
• new feature - change that adds functionality
• tests - change in tests
• infrastructure - change in infrastructure and CI
• documentation - documentation update

Tests

• added - required for new features and some bug fixes
• not needed

Documentation

• updated in # - add PR number
• needs to be updated
• not needed

Breaks backward compatibility

• Yes
• No
• Unknown

Notify the following users

List users with @ to send notifications

Other information

[icfaust]

It would be cool if you guys added some sort of ABI check like we do in oneDAL such that the VERSIONING.md must be modified upon ABI changes.

[vossmjp]

@icfaust That's a good idea, we'll look into that.

[omalyshe]

For those versions where only the RN link is provided - does it mean there were NO API changes at all? If it is not the case, then we need to list API changes for ALL versions.
I see that for the latest versions API changes are listed.

[aleksei-fedotov]

Unfortunately, neither reading in raw, nor in rich text format appeals to me. In rich text format there is lots of details that are hard follow. In raw format - the alignment is confusing.

I suggest rewriting it using different format. How about the list of lists?

For example, writing something like:

* **October 2025**

  | Library version | Binary version |
  |:---------------:|:--------------:|
  | 2022.3.0        | 12.17          |

  API/ABI Changes
  * New API: [task_arena enqueue and wait_for specific task_group](https://github.com/uxlfoundation/oneTBB/tree/master/rfcs/proposed/task_arena_waiting)
  * New API: [custom asserion handler support](https://github.com/uxlfoundation/oneTBB/tree/master/rfcs/supported/assertion_handler)
    * New ABI: `set/get_assertion_handler`
  * New API: [preview of dynamic task graph](https://github.com/uxlfoundation/oneTBB/tree/master/rfcs/proposed/task_group_dynamic_dependencies)
    * New ABI: `current_task_ptr`
    * Notes: ....
  * New ABI
  * ...

gives:

• October 2025

  Library version	Binary version
  2022.3.0	12.17

  API/ABI Changes

  • New API: task_arena enqueue and wait_for specific task_group
  • New API: custom asserion handler support
    • New ABI: set/get_assertion_handler
  • New API: preview of dynamic task graph
    • New ABI: current_task_ptr
    • Notes: ....
  • New ABI
  • ...

Alternatively, it seems like blank characters can be used to make columns have certain width. But in this case, horizontal scrolling is not convenient because the scroll bar appears at the very bottom of the table, which again can make it hard to in case the table becomes long.

[omalyshe]

I suggest clarifying that "Binary Version (Linux)".

[akukanov]

Or "runtime interface version".

[akukanov]

I suggest rewriting it using different format. How about the list of lists?

Markdown is knowingly bad for tables, except simplest ones. But the list of lists would be almost like the regular changelog, just for a subset of changes.

I would suggest moving the table out of Versioning.md into a separate file, perhaps in RST.
Another option is to make an "embedded" HTML table.

[m-fila]

Links to the release notes are being de-synchronized when a new release is added since they are counted from top. Perhaps the link could go to something stable, like github markdown release notes where release number is actually part of the link https://github.com/uxlfoundation/oneTBB/blob/master/RELEASE_NOTES.md#onetbb-20222-release-notes

Also 2022.3.0 now has the release notes.