search

jm / toml

Parse TOML. Like a bawss.
MIT License
151 stars 37 forks source link

Semantic Versioning? #19

Open 88Alex opened 11 years ago

88Alex commented 11 years ago

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.

krainboltgreene commented 10 years ago

:+1:

parkr commented 10 years ago

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.

krainboltgreene commented 10 years ago

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

parkr commented 10 years ago

Ok, but what dictates that the parser should be at v1.0 then? Why can't I have v0.1.0+toml0.2.0 or something?

krainboltgreene commented 10 years ago

You can definitely have that, but realistically people depend on the current public API in production environments.

On Wed, Aug 13, 2014 at 4:07 PM, Parker Moore notifications@github.com wrote:

Ok, but what dictates that the parser should be at v1.0 then? Why can't I have v0.1.0+toml0.2.0 or something?

— Reply to this email directly or view it on GitHub https://github.com/jm/toml/issues/19#issuecomment-52111268.

Kurtis Rainbolt-Greene, Hacker Software Developer 1631 8th St. New Orleans, LA 70115