3 ms·

Node now follows Semver. If you look through the changelog, there's more than a dozen changes that are breaking.

by quarterto 11y ago

Touche 11y ago
That doesn't answer the question. Node 4.0 was released a month ago. Why are there so many breaking changes in 1 month?
- Mchl 11y ago
  From what I understand the 4.0.0 release was to merge NodeJS and io.js into one stable product as soon as possible. 5.0.0 now goes further in integrating features that were not ready to release at that time. Further major version updates are to be less frequent.
- deleted 11y ago
  [deleted]
- cmpb 11y ago
  Mainly the upgrade of V8. The release of v5 so soon after v4 is a special scenario prompted by the odd timing of the release of the new V8. It's worth noting that v5 is not an "LTS" release (that is, it won't have the same long-term support that v4 does). I believe even number releases are LTS releases.
- netcraft 11y ago
  Thats not the question that was asked, yours is a different question. The main reason is because they are tracking v8 versions. This one hits v8 4.6 - v8 is released every 6 months and we will see node v6 in April. Really what has happened is that v4 was a bit behind, and v5 is right on schedule which is why it seems to be changing so fast.
- dragonwriter 11y ago
  > Why are there so many breaking changes in 1 month? Because that's when the planned functionality was coded, tested, and ready to deliver. Node's development model is a form of the fairly common model where you avoid wasted work (that is, work not delivering value for customers that want it) by delivering features as soon as they are ready and tested, while periodically splitting off and committing to support long-term-support releases for customers that are more concerned with longer-term stability than having the latest and greatest the moment its ready to use.
_ak 11y ago
@Touche: because they were introduced by the developers. The type of changes you make dictate the semver, but semver doesn't dictate what changes you can or can't make.

Node now follows Semver. If you look through the changelog, there's more than a dozen changes that are breaking.

Touche 11y ago

That doesn't answer the question. Node 4.0 was released a month ago. Why are there so many breaking changes in 1 month?

Mchl 11y ago
From what I understand the 4.0.0 release was to merge NodeJS and io.js into one stable product as soon as possible. 5.0.0 now goes further in integrating features that were not ready to release at that time. Further major version updates are to be less frequent.
deleted 11y ago
[deleted]
cmpb 11y ago
Mainly the upgrade of V8. The release of v5 so soon after v4 is a special scenario prompted by the odd timing of the release of the new V8. It's worth noting that v5 is not an "LTS" release (that is, it won't have the same long-term support that v4 does). I believe even number releases are LTS releases.
netcraft 11y ago
Thats not the question that was asked, yours is a different question. The main reason is because they are tracking v8 versions. This one hits v8 4.6 - v8 is released every 6 months and we will see node v6 in April. Really what has happened is that v4 was a bit behind, and v5 is right on schedule which is why it seems to be changing so fast.
dragonwriter 11y ago
> Why are there so many breaking changes in 1 month? Because that's when the planned functionality was coded, tested, and ready to deliver. Node's development model is a form of the fairly common model where you avoid wasted work (that is, work not delivering value for customers that want it) by delivering features as soon as they are ready and tested, while periodically splitting off and committing to support long-term-support releases for customers that are more concerned with longer-term stability than having the latest and greatest the moment its ready to use.

_ak 11y ago

@Touche: because they were introduced by the developers. The type of changes you make dictate the semver, but semver doesn't dictate what changes you can or can't make.