-
Notifications
You must be signed in to change notification settings - Fork 188
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
non-Semantic Versioning format #400
Comments
I've been trying to remember why we went in the other direction. I don't think at the time there was consideration given to things like mix just not working without semantic versioning. So, standardising on semantic versioning (again) is probably the right thing to do. There is a release pending to fix a bug, and as part of this I'm having to address travis being broken (no longer free for OSS), so my intention is to address versioning as well as part of this. |
Sorry for the delay with this. Just been puzzling over how to handle versioning of cloned repos (e.g. https://github.com/basho/rebar3_gpb_plugin). I would prefer not to overlap and conflict with the source repo versioning. The intention is to use e.g. 2.15.1+riak.3.0.4 |
Both erlang clients now have semantic version support: https://github.com/basho/riak-erlang-client/releases/tag/3.0.4 |
Hello,
Due to non-Semantic Versioning format (like
riak_kv-3.0.2
)mix
is not able to pull.Can't we have Semantic Versioning ?
/prakash
The text was updated successfully, but these errors were encountered: