Semantic Versioning?

[88Alex]

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]

👍

[parkr]

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]

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]

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]

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
#19 (comment).

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