Define versioning policy?

Hi all,

Is it possible to get some versioning policy around mvnd.
Statements I would expect are:

1. is it using semver (if not what does mean major/minor/patch)
2. how does it follow maven and how does it relate to? ("it follows each minor of 3.x and there is a compatibility matrix for the equivalence" or "it is compatible with 3.x and rely on the env maven" kind of statement - I know both are not accurate as of today but just trying to illustrate the idea)
3. Any plan to support multiple maven branches?
4. What about security fixes in mvnd or maven stack?

Thanks.

No file, test, or entry point is named. Start by reviewing the current mvnd and Maven versioning and release documentation alongside the 14-comment discussion, then document agreed answers about SemVer, Maven compatibility and branches, and security fixes; done means the policy is recorded clearly.

Written by the indexing model from the issue text.