The difference between 0.x.y in semver and 1.0.0+ is a commitment to take bumping majors seriously. 1/
-
-
That deprives you of the ability to communicate "I'm going to make breaking changes at a slow pace, with a lot of warning" 3/
-
This stuff is not about individual projects, which can absorb small changes over time, but about ecosystems 4/
-
Ecosystems need a rough idea of the approximate pace of breakage, so packages can coordinate upgrades. 5/
-
This is especially important when packages start depending on other packages, etc. 6/
-
TLDR Semver and 1.0 are not just about formally defining breakage, but also about making a commitment to managing the pace of breakage 7/7
-
@wycats okay but where is that second bit in the semver specification? -
@davidlymanning the semver FAQ is quite clear that the intent of the majors is to slow down the pace of breakage. - 1 more reply
New conversation -
-
-
@wycats I don't see any problem in high major version numbers, but I see problems in introducing breaking changes with the 0.x.y excuseThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.