2 ms·
As per semantic versioning, 0.x.y is for development. That's not to say that code quality will be necessarily lower, but the API and functionality is expected/a
by akerl_ 13y ago
As per semantic versioning, 0.x.y is for development. That's not to say that code quality will be necessarily lower, but the API and functionality is expected/allowed to fluctuate prior to 1.0.0.
For more info on semantic versioning: http://semver.org/spec/v2.0.0.html http://semver.org/spec/v2.0.0.html
Your point regarding npm itself being beyond 1.0.0 is fully valid, I just wanted to clarify the reason for certain expectations existing based on version number.
- iends 13y agonode does not use semantic versioning.
- akerl_ 13y agoHaving looked, I can't find any link citing that one way or the other, but that doesn't change the fact that enough things these days do adhere to semantic versioning that many people expect certain things based on the version number.
- nilved 13y agonode.js decided uses very non-semantic versioning. It's genarally understood that a 0.x release isn't production-ready, but node.js is widely considered production-ready and in fact every even-numbered release below 1.0 is considered stable. That's a pretty arbitrary and nonsensical scheme if you ask me, but you're not. The bottom line is that backwards incompatible changes aren't expected for a 0.x.y release where x is even.
- 1stop 13y agoThen there shouldn't be an expectation that it is "enterprise ready" at all, right? :P