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!
And it's what bad actually. Too much breaking changes, it makes your code legacy in less than a year. Edit : I've been downvoted and I just see that my comment is not that explanatory. It's not really bad as for bad for everyone. In a small where development is not the core activity, a language that introduce too many breaking change is not likely to be a good choice. Because the development will be slow, the app will have an outdated language by the times it goes out. For example, I've got an app which I started to develop a year ago. With Vue, it's still Vue 2, I can deploy the app with the latest version without even caring about about upgrading. It's not about skill or whatever, it's just about cost.
Yep, I've had to bump major versions for tiny things sometimes. It feels a bit wrong upgrading a major version for something so small, but a breaking change is a breaking change.
78
u/DerpsMcGeeOnDowns Oct 19 '18
It’s just proper semver man. Nothing crazy. If there’s a major breaking change, it’s bumped. Simple.