+1 from me! In MicroProfile, I got semantic versioning utilized in MicroProfile Config and then it was adopted by the subsequence specifications (I think all of them). Semantic Versioning policy played an essential role towards working out which packages have major or minor or no changes. The good news is that there is a semantic versioning plugin. With this plugin, when we update any APIs, the tool will work out whether we introduced any backward incompatible changes. At the moment, there was no automation tool available in Jakarta EE and we were pretty manually working out whether breaking changes were introduced. Sometimes it was not easy.
With the current issue CDI is facing regarding the impacting on Transaction, if we semantic versioning the packages, we can work out whether the packages Transaction uses have major/minor/no updates. Then, we can tell Transaction to perform major/minor/no updates.
p.s. I brought up the idea of adopting semantic versioning in Jakarta EE platform calls on 24th August 2021. You can see the discussion
here (2021-08-24 and then 08-31). There was no objection from the platform group. The spec group can try and then decide.
Thanks
Emily
