Skip to content

Conversation

@bluca
Copy link
Member

@bluca bluca commented Nov 6, 2025

No description provided.

bluca added 3 commits November 6, 2025 21:59
All specs are MAJOR.MINOR. MAJOR is incremented on breaking changes,
MINOR on incompatible changes. A 0.x is experimental.
filename/MAJOR.MINOR for git tag for each new version of a given spec.
All at 1.0 apart from LFHS and VOA which are 0.1 as WIP
Copy link
Member

@keszybz keszybz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one question.


## License

All specifications are licensed under [CC-BY-4.0](https://spdx.org/licenses/CC-BY-4.0.html).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All the individual spec files have a SPDX header with CC-BY-4.0, so this just adds a note that is more visible to readers.

Comment on lines +51 to +59
All specifications are versioned.

The versioning format is MAJOR.MINOR.
Compatible changes increment the MINOR version.
Incompatible changes increment the MAJOR version and reset the MINOR version to `0`.

Work in progress specifications have a MAJOR version of `0`.

A `filename/MAJOR.MINOR` git tag will be created when a new version of a given spec is released.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, this is great. I had something like this in mind, but the wording is particularly concise and clear.


| Version | Changes |
|---------|---------|
| 0.1 | Work in progress |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I think we could put 1.0 here. Do you anticipate any bigger changes?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It had an important change only two days ago, so wanted to be a bit careful here and get the general structure right. We can easily do 1.0 in a separate PR if we feel it's ready

@brauner brauner merged commit 36dfb51 into uapi-group:main Nov 6, 2025
1 check passed
@bluca bluca deleted the version branch November 6, 2025 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants