5 ms·

Uh, didn't 4.0.0 just come out? Seems rather quick, no? How much could possibly have changed? The buffer creation change warrants a point bump?

bryanlarsen 11y ago
Choose 2: - semver - small, infrequently changing major & minor version numbers - large, active project
- wolfgke 11y ago
  No, choosing all 3 is possible, too: Let semver hold, we have to prove that choosing 2 and 3 is then possible, too: For 2: Since semver implies that the version numbers increase fast with the number of releases, 2 can hold, if we only rarely release new versions. Note that this does not imply that it isn't large and active. For an example: If creating new releases takes a lot of time, few new versions will be releases, but the project can still be very active. To give a (slightly artificial) example: If (because of quality standards of the project) any release will also contain a machine-checked proof of correctness, creating a new release will take a long time. TLDR: A large, active project that only rarely releases new versions, but names them semantically has all three properties.
  - tracker1 11y ago
    There was a change that added or significantly changed functionality... this necessitates asemver minor bump. Point releases are generally for non-breaking patches or bug fixes.
    - wolfgke 11y ago
      I know what semver is. But my claim was that if you want all three claimed properties (which are claimed as incompatible), you can have them all.
tehbeard 11y ago
http://semver.org/ http://semver.org/ From the changelog it looks to be inline with this.
- HorizonXP 11y ago
  Ah yes, it does. Thanks!
untog 11y ago
There's no obligation to immediately update to 4.1.0 if you don't want to. Since there are no breaking changes all the same modules should work.
skarap 11y ago
9 days. There is a bunch of commits, sure. But if nodejs team is really aiming for stability as was stated in the 4.0.0 announcement IMO they should give it longer time to stabilize.

bryanlarsen 11y ago

Choose 2: - semver - small, infrequently changing major & minor version numbers - large, active project

wolfgke 11y ago
No, choosing all 3 is possible, too: Let semver hold, we have to prove that choosing 2 and 3 is then possible, too: For 2: Since semver implies that the version numbers increase fast with the number of releases, 2 can hold, if we only rarely release new versions. Note that this does not imply that it isn't large and active. For an example: If creating new releases takes a lot of time, few new versions will be releases, but the project can still be very active. To give a (slightly artificial) example: If (because of quality standards of the project) any release will also contain a machine-checked proof of correctness, creating a new release will take a long time. TLDR: A large, active project that only rarely releases new versions, but names them semantically has all three properties.
- tracker1 11y ago
  There was a change that added or significantly changed functionality... this necessitates asemver minor bump. Point releases are generally for non-breaking patches or bug fixes.
  - wolfgke 11y ago
    I know what semver is. But my claim was that if you want all three claimed properties (which are claimed as incompatible), you can have them all.

tehbeard 11y ago

http://semver.org/ http://semver.org/ From the changelog it looks to be inline with this.

HorizonXP 11y ago
Ah yes, it does. Thanks!

untog 11y ago

There's no obligation to immediately update to 4.1.0 if you don't want to. Since there are no breaking changes all the same modules should work.

skarap 11y ago

9 days. There is a bunch of commits, sure. But if nodejs team is really aiming for stability as was stated in the 4.0.0 announcement IMO they should give it longer time to stabilize.