Open gajanan-choudhary opened 2 months ago
A provisional version 1.4 of oneAPI Specification was created a few days back.
The sparse BLAS domain in oneMKL specification was overhauled and rewritten (no backward compatibility whatsoever) in June 2024 in #522
Shouldn't this trigger a major-version update of the oneAPI Specification to 2.0 instead of 1.4?
Tagging: @rscohn2, @spencerpatty, @Rbiessy, @sknepper, @mkrainiuk, @vmalia
Components can choose to have their own version. onemkl can declare that the next version is 2.x or 2025.x
In hindsight, I would have used calendar versioning for the combined document.
A provisional version 1.4 of oneAPI Specification was created a few days back.
The sparse BLAS domain in oneMKL specification was overhauled and rewritten (no backward compatibility whatsoever) in June 2024 in #522
Shouldn't this trigger a major-version update of the oneAPI Specification to 2.0 instead of 1.4?
Tagging: @rscohn2, @spencerpatty, @Rbiessy, @sknepper, @mkrainiuk, @vmalia