Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Semantic versioning #4647

NiklasBr opened this issue Jul 9, 2019 · 1 comment


None yet
2 participants
Copy link

commented Jul 9, 2019

Feature Request

Fully commit to use Semantic Versioning.

Feature description

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:

  • Incrementing the major version number, or
  • Adding a compatibility layer until the major version number can be increased, or
  • Waiting with these changes until you feel a new major version is warranted, for example committing these to a 7.x branch while 6.x is the current stable release.

This comment has been minimized.

Copy link

commented Jul 9, 2019


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.