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

versioning problem #3735

Closed
josephzhao opened this issue Apr 20, 2016 · 2 comments
Closed

versioning problem #3735

josephzhao opened this issue Apr 20, 2016 · 2 comments

Comments

@josephzhao
Copy link

I hope for the sonata project can use same version number for all bundle compatible, some times it difficult to find out all bundles version which compatible with each other, I just download sandbox , and when I use composer.phar to update all bundles, there is still errors.

if we can use 2.3.* or 2.4.* for all Sonata bundles that should be much better for us.

Thanks

@ju1ius
Copy link
Contributor

ju1ius commented Apr 20, 2016

Looks like this is not going to happen anytime soon.

@soullivaneuh
Copy link
Member

I hope for the sonata project can use same version number for all bundle compatible, some times it difficult to find out all bundles version which compatible with each other

We decide starting #3053 to strictly follow semver and semver is not the way you describe.

I understand your problem that is real for actual versions of sonata project but just tag same version for each project is not the solution.

The solution is to push more releases and be very careful about BC.

Please refer to #3053 and #3731 and also sonata-project/dev-kit to see what is going on for the future.

Regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants