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

last tagged version 0.6.0 or 0.5.2 #51

Open
lalop opened this issue Apr 24, 2014 · 4 comments
Open

last tagged version 0.6.0 or 0.5.2 #51

lalop opened this issue Apr 24, 2014 · 4 comments

Comments

@lalop
Copy link

lalop commented Apr 24, 2014

Hello,
Watching the commit history it seems that tag 0.5.2 is newer than 0.6.
Is that normal ?
Which one is the last stable version ?

@lalop lalop changed the title last tagged version 6.0 or 5.2 last tagged version 0.6.0 or à.5.2 Apr 24, 2014
@lalop lalop changed the title last tagged version 0.6.0 or à.5.2 last tagged version 0.6.0 or 0.5.2 Apr 24, 2014
@msheakoski
Copy link

I've been using "dev-master#2401140dae" without any issues. It contains fixes for issues that were not present in 0.5.2/0.6.0.

@lalop
Copy link
Author

lalop commented May 7, 2014

ok but maybe a new tag for the current stable version is welcome, is'nt it ?

@msheakoski
Copy link

Certainly, but I have no control over that. Until then, I use "jaz303/phake": "dev-master#2401140dae" in my composer.json and don't mind because I haven't run into any further issues. Since it's locked to that commit, there are no surprise updates either.

@sagikazarmark
Copy link

In semantic versioning support versions are possible. So the latest stable is the "biggest version", but bugfixes for older (major) versions can also be released so that applications supporting old API can also be bugfixed.

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