There's one more situation where you should use semver: where you simultaneously develop the next version, which will not be ready for release in the next coupl

There's one more situation where you should use semver: where you simultaneously develop the next version, which will not be ready for release in the next couple of weeks, and provide hotfixes to the public one. May be the end user won't be making a decision which version to use, but your qa will certainly experience both at the same time, so they should have some understanding of what's the magic version of the product, aside from release date.