Skip to content
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.

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

Requirement GV.03 - Backwards Compatibility #245

Open
absoludity opened this issue Jan 10, 2025 · 0 comments
Open

Requirement GV.03 - Backwards Compatibility #245

absoludity opened this issue Jan 10, 2025 · 0 comments

Comments

@absoludity
Copy link
Contributor

Impacted sections

Issue Description

The current text states that:

New versions of UNTP SHOULD be backwards compatible with earlier versions and each version MUST remain active and supported for a minimum of 2 years - so that implementers can have confidence in the durability of their investment.

which sounds like an over-promise hidden behind a "SHOULD". Assuming that UNTP will follow semantic versioning, I think it should promise a little less but as a MUST (even if it makes the sentence more complex).

Something like: New minor versions of UNTP MUST be backwards compatible with earlier versions. Each major version MUST remain active and supported for a minimum of 2 years - so that implementers can have confidence in the durability of their investment.

Just food for thought. Happy to push a PR if people agree.

Interestingly, the governance page does mention major/minor versions - it's just here on the requirements page that it over-promises a bit (IMO) by not mentioning major/minor versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant