4 ms·
Okay let me spell it out for you: No one wants a major version bump in Bundler in order to change the primary rubygems URL because historically there is a lot
by dasil003 14y ago
Okay let me spell it out for you:
No one wants a major version bump in Bundler in order to change the primary rubygems URL because historically there is a lot of potential pain in Bundler updates, and so you better be getting something new that's worth the pain, not just a superficial change that happens to break compatibility only as a technicality.
- dragonwriter 14y ago> No one wants a major version bump in Bundler in order to change the primary rubygems URL because historically there is a lot of potential pain in Bundler updates SemVer seems pretty much tangential to that, that's a problem with the particular history of the particular project. If the original claim had been "Bundler's history of major version updates means that they don't want to bump their major version; combined with their commitment to SemVer, that means that any backward incompatible changes are avoided", rather than just that SemVer alone led to people in general seeking to avoid backward-incompatible changes, I wouldn't have challenged it.