6 ms·

I'm so out of the loop… Feels like a week ago everyone talked about how cool and performant v2 will be when it's finally out of the beta and officially ready fo

I'm so out of the loop… Feels like a week ago everyone talked about how cool and performant v2 will be when it's finally out of the beta and officially ready for production, and now there is v4 release. What's going on with versions?

ErikAugust 10y ago
SEMVER - Semantic Versioning - http://semver.org/ http://semver.org/
- manquer 10y ago
  Not exactly semver either, Angular 4 is backward compatible with 2.x.x. Following semver would mean it should continue to be in 2 series
  - WorldMaker 10y ago
    It makes breaking changes that might break some users. That is following semver. Semver doesn't follow backward compatibility in the major number, it follows potential breaking changes that will impact downstream consumers.
- usrusr 10y ago
  Aka when in doubt, increment leftmost, also we won't tell you wether we did a complete conceptual overhaul or just found a corner case that is provably incompatible. And I really thought it would be good.
bsimpson 10y ago
semver
dreamache 10y ago
All of the Angular modules were 2.x.x with exception to the router, which was version 3.x.x. So to keep all of them at the same major version, they pushed everything to version 4. Also, the jump from AngularJS (1) to Angular 2 was drastically different. Going from 2 to 4 however is much less significant in terms of breaking changes. You won't have to relearn hardly anything if you already know 2.
Eric_WVGG 10y ago
"Angular 1" is now known as Angular.js and is effectively at the end of its line. Angular 2+ is now simply Angular. All new releases follow a naming of version X.Y.Z where X indicates breaking changes, Y non-breaking new features, and Z is bug fixes. Version 3 is being skipped over due to poor naming of the related Angular Router lib. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-be.html http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-...
- wernercd 10y ago
  Damn... I was really hoping for Angular 16 next year...
  - chiefalchemist 10y ago
    16 will be skipped for...no reason what so ever.
  - rimliu 10y ago
    They should just name with a year. So in 2018 you'd know that Angular 2017 is so last year…
- skybrian 10y ago
  There is also AngularDart, which has forked and isn't following the same numbering scheme: https://webdev.dartlang.org/angular https://webdev.dartlang.org/angular
- cheapsteak 10y ago
  It seems that lockstep versioning makes semantic versioning less meaningful A major version bump for a module could signal a breaking change, or it could just be due to the packages it's locked to having had a breaking change
  - humanrebar 10y ago
    A breaking change in your dependencies is a breaking change for you. If it weren't, minor version upgrades would cause you to pull in incompatible dependencies. This is why keeping your dependency list as tiny as possible is imperative.
louhike 10y ago
It is explained in the first sentence of the article.

ErikAugust 10y ago

SEMVER - Semantic Versioning - http://semver.org/ http://semver.org/

manquer 10y ago
Not exactly semver either, Angular 4 is backward compatible with 2.x.x. Following semver would mean it should continue to be in 2 series
- WorldMaker 10y ago
  It makes breaking changes that might break some users. That is following semver. Semver doesn't follow backward compatibility in the major number, it follows potential breaking changes that will impact downstream consumers.
usrusr 10y ago
Aka when in doubt, increment leftmost, also we won't tell you wether we did a complete conceptual overhaul or just found a corner case that is provably incompatible. And I really thought it would be good.

bsimpson 10y ago

semver

dreamache 10y ago

All of the Angular modules were 2.x.x with exception to the router, which was version 3.x.x. So to keep all of them at the same major version, they pushed everything to version 4. Also, the jump from AngularJS (1) to Angular 2 was drastically different. Going from 2 to 4 however is much less significant in terms of breaking changes. You won't have to relearn hardly anything if you already know 2.

Eric_WVGG 10y ago

"Angular 1" is now known as Angular.js and is effectively at the end of its line. Angular 2+ is now simply Angular. All new releases follow a naming of version X.Y.Z where X indicates breaking changes, Y non-breaking new features, and Z is bug fixes. Version 3 is being skipped over due to poor naming of the related Angular Router lib. http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-going-to-be.html http://angularjs.blogspot.com/2016/12/ok-let-me-explain-its-...

wernercd 10y ago
Damn... I was really hoping for Angular 16 next year...
- chiefalchemist 10y ago
  16 will be skipped for...no reason what so ever.
- rimliu 10y ago
  They should just name with a year. So in 2018 you'd know that Angular 2017 is so last year…
skybrian 10y ago
There is also AngularDart, which has forked and isn't following the same numbering scheme: https://webdev.dartlang.org/angular https://webdev.dartlang.org/angular
cheapsteak 10y ago
It seems that lockstep versioning makes semantic versioning less meaningful A major version bump for a module could signal a breaking change, or it could just be due to the packages it's locked to having had a breaking change
- humanrebar 10y ago
  A breaking change in your dependencies is a breaking change for you. If it weren't, minor version upgrades would cause you to pull in incompatible dependencies. This is why keeping your dependency list as tiny as possible is imperative.

louhike 10y ago

It is explained in the first sentence of the article.