Using Semantic Versioning to manage API changes ?

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 https://github.com/open-coap/java-coap/issues/48#issuecomment-1531502562:

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.

open-coap / java-coap

Using Semantic Versioning to manage API changes ? #53