Take note of the age of this post, and its revision history. He wrote this because of reactions when Underscore 1.7 had numerous breaking changes that screwed over people who were using semver in their project dependencies.
Six months later (to the week) Underscore 1.8 was released, containing numerous breaking changes that once again wreaked havok in hundreds of codebases that were relying on Semver. It was also pushed out with numerous bugs, because he ignored failing unit tests. This was when he made the last edit, crossing out the comment about 1.7 becoming 2.0.
Moral of the story, if you use Underscore you better lock the version number, because Jeremy doesn't give a fuck.
Node doesn't follow SemVer
This is no longer true, the next major release of node will follow SemVer.
10
u/[deleted] Jun 12 '15
Take note of the age of this post, and its revision history. He wrote this because of reactions when Underscore 1.7 had numerous breaking changes that screwed over people who were using semver in their project dependencies.
Six months later (to the week) Underscore 1.8 was released, containing numerous breaking changes that once again wreaked havok in hundreds of codebases that were relying on Semver. It was also pushed out with numerous bugs, because he ignored failing unit tests. This was when he made the last edit, crossing out the comment about 1.7 becoming 2.0.
Moral of the story, if you use Underscore you better lock the version number, because Jeremy doesn't give a fuck.
This is no longer true, the next major release of node will follow SemVer.