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.
Given 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
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.
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.