3 ms·
MRI didn't follow semver up until recently, and even now it has some caveats about it. Ruby as an ecosystem doesn't really care for semver. Some projects follo
by awj 12y ago
MRI didn't follow semver up until recently, and even now it has some caveats about it.
Ruby as an ecosystem doesn't really care for semver. Some projects follow it anyways, which I can respect, but they aren't the norm.
- matdes 12y agoMRI still doesn't follow semver but core doesn't really give a crap.
- steveklabnik 12y agoThey claim "Semantic Versioning type" versioning, which is, of course, not SemVer, but I think what your parent was referring to. https://www.ruby-lang.org/en/news/2013/12/21/ruby-version-policy-changes-with-2-1-0/ https://www.ruby-lang.org/en/news/2013/12/21/ruby-version-po...
- Argorak 12y agoMRI picked its version scheme in the 90s, long before "semver" was a thing. That kind of version scheme wasn't unusual in that time. Problems due to legacy don't make a good argument. The Ruby system cares for semver in general and it is propagated there a lot, but I agree: it certainly isn't uniform.