4 ms·

Node uses semantic versioning: http://semver.org/ http://semver.org/

• randallsquared 14y ago
  Not perfectly: "If your software is being used in production, it should probably already be 1.0.0."
  • dragonwriter 14y ago
    > Not perfectly: "If your software is being used in production, it should probably already be 1.0.0." "Probably" is, ipso facto, not normative.
  • niggler 14y ago
    The public API is not stable, hence a 0.xx number is justified.
    • randallsquared 14y ago
      That doesn't seem to match what the semver.org site says. Node's public API is not changing in a backward-incompatible way every day (or even every week, or every month). The software is widely used in production. I think node 1.0.0 should have been some time ago, and this release should have bumped the major version again.
      • niggler 14y ago
        "Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable." -- from semver.org "The software is widely used in production." Depending on how you define the "public API", things have changed from 0.8 to 0.10 (streams API, for example). Your definition of Node 1.0.0 is based on your conception of how others are using node. People can use experimental software in high-profile places without deeming the underlying technology stable. "Node's public API is not changing in a backward-incompatible way every day (or even every week, or every month). " Also: in general, development is highly nonlinear. I would say the API is stable when the core developers deem it stable.