Skip to content

Incomplete documentation about spec versioning #551

Open
@vmalia

Description

@vmalia

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 about when to rename the specification's major or minor version.

Expected

  1. The spec should define what a major and minor version update mean for the specification and the underlying product. Same for the revision.
  2. The versioning scheme must be programmatically possible to implement, similar to semantic versioning.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions