Using Semantic Versioning to manage API changes ?

[sbernard31]

This issue aims to discuss about how to manage API changes in the future (not a short term question):

• should Semantic Versioning) be used ? Or anything else ?
• which tooling can be used ?

This was triggered by #48 (comment):

Not the first time when I update java-coap there is API break between 2 minor version, for now this is not a problem as we are in development phase, but if we release a stable version of Leshan including java-coap dependency, that could be an issue. Did you already consider to maybe move to Semantic Versioning ?

Yes, I am aware of that. When needed, we can switch to be more strict with API changes.

[sbernard31]

About tooling, it exist this maven plugin : https://revapi.org/revapi-site/main/index.html

[szysas]

Closing this for now, in this project we need to be able to do fast and small changes and treat every commit to main branch as production ready.

[sbernard31]

When needed, we can switch to be more strict with API changes.

Just to clarify, does it mean that ☝️ is still true ? or that means ☝️ is no more goal for the future ?

[szysas]

Yes, it is true, when needed, we can switch to be more strict with API changes.