You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently had a customer request to provide APIs in Intel(R) oneMKL, for providing the version of the oneAPI spec that the product is compliant with.
During this investigation, I found that the oneAPI spec repository uses https://github.com/uxlfoundation/oneAPI-spec/blob/main/oneapi-doc.json file to define a version string, but the specification itself does not have any guidelines about when to rename the specification's major or minor version.
Expected
The spec should define what a major and minor version update mean for the specification and the underlying product. Same for the revision.
The versioning scheme must be programmatically possible to implement, similar to semantic versioning.
The text was updated successfully, but these errors were encountered:
Description
We recently had a customer request to provide APIs in Intel(R) oneMKL, for providing the version of the oneAPI spec that the product is compliant with.
During this investigation, I found that the oneAPI spec repository uses https://github.com/uxlfoundation/oneAPI-spec/blob/main/oneapi-doc.json file to define a version
string
, but the specification itself does not have any guidelines aboutwhen
to rename the specification's major or minor version.Expected
revision
.The text was updated successfully, but these errors were encountered: