-
Notifications
You must be signed in to change notification settings - Fork 38
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
Semantic Versioning? #19
Comments
👍 |
Pardon my ignorance, but why should we already be at 1.0.0? Can you cite the SemVer spec please where it says that? We're waiting on TOML v1.0.0 to release a compatible version of this gem. |
The gem version shouldn't be dependant on the spec version. For that, you'd specify in the build metadata: v1.0.0+toml1.0.0 |
Ok, but what dictates that the parser should be at v1.0 then? Why can't I have |
You can definitely have that, but realistically people depend on the On Wed, Aug 13, 2014 at 4:07 PM, Parker Moore notifications@github.com
Kurtis Rainbolt-Greene, Hacker |
Does your project use the Semantic Versioning system? (semver.org) Because if it does, you should already be at 1.0.0-; one of my Ruby projects has your gem as one of its dependencies. It would be much more convenient for me (and for others) if you used SemVer.
The text was updated successfully, but these errors were encountered: