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
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.
The text was updated successfully, but these errors were encountered:
Impacted sections
Issue Description
The current text states that:
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.
The text was updated successfully, but these errors were encountered: