Fully commit to use Semantic Versioning.
With the introduction of Composer support in 5.x updating is much easier from a technical perspective, but it is still not clear if we can trust minor and patch versions fully, for example #4645 which has some nice changes but is a BC break and appears soon to be ready to merge.
From my perspective it would add a lot of confidence in releases which are tagged as minor and patches if Pimcore promises not to add BC breaking changes without either:
馃憤
Can't believe no one from the Pimcore team took the responsibility for this yet :cry:
https://semver.org/#why-use-semantic-versioning
Starting with 7.0 we're going to fully commit to semver and there will be guidelines similar to https://symfony.com/doc/current/contributing/code/bc.html
For the 6.x branch we promise to be as close to semver as possible.
馃憤 馃憤 馃憤 Thanks @brusch!

Most helpful comment
Starting with 7.0 we're going to fully commit to semver and there will be guidelines similar to https://symfony.com/doc/current/contributing/code/bc.html
For the 6.x branch we promise to be as close to semver as possible.