3 ms·

That is asinine. Why not change it in 5.x->6.0 if they knew it was a problem. Why even use version numbers at that point? Just use DateVer or 0ver at that point

• dragonwriter 5y ago
  > Why not change it in 5.x->6.0 if they knew it was a problem Because Rails explicitly has a versioning policy where minor versions are equivalent to SemVer major versions (but with deprecation notice in a previous minor version) and where major versions are also SemVer major with subjective significance distinctions; they call it “shifted SemVer”. https://guides.rubyonrails.org/maintenance_policy.html https://guides.rubyonrails.org/maintenance_policy.html This is somewhat obnoxious, but not as bad as saying you use real SemVer and then brazenly breaking things in minor releases.
  • kortex 5y ago
    Sure, but like, you don't have to break code on .Y changes. Changing semantics of a query operator is something worth saving for a "big major" update, if you change it all. Some breaking changes are really obvious and easy to catch. Others can introduce pernicious bugs which slip through tests. The change Mongoid is solidly the latter. And yeah, they say they use actual Semver.
    • dragonwriter 5y ago
      > Changing semantics of a query operator is something worth saving for a "big major" update, if you change it Arguably, it was so important that they did a big major update just to deprecate it.