3 ms·
No change between a v4 and v5 should be “radical”. Sure make changes, even breaking changes but “radical” does not inspire confidence that the migration will b
by simonbarker87 3y ago
No change between a v4 and v5 should be “radical”.
Sure make changes, even breaking changes but “radical” does not inspire confidence that the migration will be straightforward or that the people running the project have any respect for what users have already built.
I hope this is just Rebase style hype and that in reality the changes are more measured than implied here.
- bastardoperator 3y agoGiven a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes <-- You are Here MINOR version when you add functionality in a backward compatible manner PATCH version when you make backward compatible bug fixes
- simonbarker87 3y agoNot disputing you can have breaking changes. Radical implies Angular v1 to v2 types changes, which was disastrous for a lot of people who had built large complex apps on v1 that then had to be maintained for years because a v2 rewrite was too big.