Semantic versioning
ioquatix opened this issue · 4 comments
Is it possible you can use semantic versioning, e.g. $major.$minor.$patch in your releases?
All people need to do to track the correct branch is write "~> 2.2", but they might even prefer to be more specific.
I've addressed this in the past and have made it part of the README.
It is unnecessary to specify the version as 2.x.y because RubyGems (and therefore Bundler) is already smart enough to recognize that 2.3 is implicitly 2.3.0. Because I use patch release for actual patches (only bug fixes, or MIME type typographical fixes), there are very few of these. I'm not going to be releasing 2.3.0, 2.4.0, etc. I'm never going to refer to them as those versions in documentation, and I know that all of the software in use for versions in Ruby understand the implicit .0 at the end of a version (infinitely so, if necessary).
As a note, in 18 releases tracked by RubyGems.org, there have been four releases that included a patch-level. That's a bit less than 25% of the releases, and with the plans I have for maintaining mime-types in the future, they should be an even smaller percentage (my plan is to release roughly monthly with at least type updates, and all of those types will be minor or major). I'm a little behind on that schedule—the paying job, after all—but I am moving forward with it.
Cool, yeah I read the README - thanks for the additional clarifications.
No problem. My decision here is deliberate and based on experience with the tools Ruby provides. I'll do patch releases if I have to, but my goal is to make it so that I don't have to.