New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Versioning Discussion #1082

Open

egekorkan opened this issue Mar 8, 2023 · 1 comment

Labels

Contributor

egekorkan commented Mar 8, 2023

In the TD Call, we had an initial discussion on how to version:

Individual Specifications (TD 1.0, TD 1.1, TD 2.0 etc.)
A family of WoT Specifications

This should be a decision we take that is not tied to a charter. Some initial viewpoints:

A similar approach to CSS Levels: https://www.w3.org/Style/2011/CSS-process.en.html
Each binding/profile mentions the version of TD they support. Semantic versioning can be used to track compatibility.
- They say the major version they support
- If they do not support the breaking changes in the new major version, they are not in the registry of the new major version.

mmccool added the Planning label

Contributor Author

egekorkan commented Jan 24, 2024 •

edited

Loading

TD call of 24.01:

Additionally, we need to also validate if the changes break existing implementations and measure the impact in case of influence on the existing implementations.
We need to make sure to tag version changes so that tools can pick up on that. E.g. the TypeScript types generation via the Scripting API TF.

egekorkan mentioned this issue

Carry over changes from the TD repo w3c/wot-resources#19

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment