Semantic versioning of MKPs

We are not enforcing the semantics of the versioning. If you used to versionise using “1”, “2”, “3”, all you have to do is use “1.0.1”, “1.0.2”, “1.0.3” now.

The problem here is (one that we often face in Checkmk): We have to have a way that is not too complicated in simple cases and allows for cases where things are a bit more convoluted.
You are right: Most MKPs don’t add new features during their lifetime. I see it this way: If you wanted to, you could now convey this information by the version number. If you choose not to: No harm done.