SemVer is nice but not nescessarily - I'd rather a project not follow semver but have a clear deprecation cycle they follow all other things been equal.
version n, we are going to remove foo
n+1 foo is marked as deprecated
n+2 foo is removed.
That I can work with since it gives me a change to refactor with clear ideas of what will break.
The symfony team get my absolute respect for the way they handle this over in PHP land,it gives me a high degree of re-assurance that we can reliably shift versions with minimal friction since they are alerting me though deprecation notices that I can then go resolve.
SemVer is nice but not nescessarily - I'd rather a project not follow semver but have a clear deprecation cycle they follow all other things been equal.
version n, we are going to remove foo n+1 foo is marked as deprecated n+2 foo is removed.
That I can work with since it gives me a change to refactor with clear ideas of what will break.
The symfony team get my absolute respect for the way they handle this over in PHP land,it gives me a high degree of re-assurance that we can reliably shift versions with minimal friction since they are alerting me though deprecation notices that I can then go resolve.