Why is everyone downvoting people who are questioning Angular's upgrade/versioning strategy?
React is currently at 16.5 and the inital "major" release of this version (16.0) was back in September of 2017. So it's been over a year at a single "major" version.
Vue 2.0 was released September of 2016 and is currently at 2.15.17. So it's been over two years since a "major" version.
Angular 6.0 was released in May of 2018 and is now at 7.0 in October of 2018. So.... five months before a new "major" version?
Considering the debacle of "ng 1" to Angular and that incompatibility, it should be fairly easy to understand why people are side eyeing the release strategy of the Angular team. I mean, generally "major" would mean something pretty majorly different, and that just doesn't seem to be the case here.
When they announced Angular 2, they said they would be doing a major release every 6 months. I wonder if they are consistently introducing breaking changes every release.
Yes, technically upgrading TypeScript to 3.1 is a breaking change. For most applications, it will not cause any side effects or require any fixing, but in some obscure cases it will need some fixes applied (e.g. as TypeScript has got better / more strict at detecting type anomalies). I upgraded our codebase today after the release was announced: >10k TS files, took me a couple of hours to read the release notes, upgrade packages and test everything out and get it deployed - hit no issues at all this time!
That is one approach. Not the only one. For example, when I worked with Southwest Airlines their commerce site used this structure X.Y.Z. where X are the last two digits of the year. Y is the number of the year's sprint which usually matched the month, and Z was the number of post activation hotfixes deployments that had to be done.
So they just aren't using semantic versioning? Major version upgrades should be breaking. If the changes don't break the API then it should just be a minor version upgrade.
5 to 6 was a nightmare but that was mostly due to rxjs going from 5 to 6 and the auto update too not working very well on our codebase. We also didn't want to leave the rxjs compat lib in there.
Besides that, yeah I agree, it's been pretty smooth upgrades the whole way through.
Depends if you're using the feature that breaks. 5 - 6 was a massive breaking change for me because I used a load of the RX stuff. I think the poster must have had some changes because RX is pretty integral into Angular - but if he didn't, then he might have had no refactoring. Maybe the auto update tool worked for him and he's forgotten!
It's still a breaking change to the API though, he's just not using that particular change.
Hell, updating to the latest version of TypeScript will be technically a breaking change, but very unlikely to actually impact anyone.
The animation system was changed, a breaking change. I'm guessing a lot of people's applications don't use Animations and they never needed to care. Still a breaking change.
There hasn't been many breaking changes since v.2, and ever since 4.x most updates are quite trivial and ever since v6 you can run a CLI command that automatically fixes/warns you about deprecated features. v5 to v6 had major changes to rxjs imports but this could be remedied by importing a compatibility library.
I haven't experienced any major pains ever since the early days of 2.x and RC versions breaking things every month.
96
u/thatgibbyguy Oct 19 '18
Why is everyone downvoting people who are questioning Angular's upgrade/versioning strategy?
React is currently at 16.5 and the inital "major" release of this version (16.0) was back in September of 2017. So it's been over a year at a single "major" version.
Vue 2.0 was released September of 2016 and is currently at 2.15.17. So it's been over two years since a "major" version.
Angular 6.0 was released in May of 2018 and is now at 7.0 in October of 2018. So.... five months before a new "major" version?
Considering the debacle of "ng 1" to Angular and that incompatibility, it should be fairly easy to understand why people are side eyeing the release strategy of the Angular team. I mean, generally "major" would mean something pretty majorly different, and that just doesn't seem to be the case here.