News for hackers. Stuff that matters.

A comment on A strong commitment to backwards compatibility means keeping your mistakes. Parent comment

Re:A strong commitment to backwards compatibility means keep... by account42 on Wednesday June 16, 2021 @04:05AM (#27526088)
> One, if not the most important part of semver is communicating the nature of the changes, and in particular, how that change affects the use.

Yes, SemVer communicates breaking changes, but only after they have happened. The point is that you should have a migration path ready long before the old API is no longer available.

[ Parent | on HN ]
Re:A strong commitment to backwards compatibility means keep... by okamiueru on Wednesday June 16, 2021 @06:56AM (#27527051)
What do you mean by "after they have happened"?

The changes to an updated library don't affect you until you have upgraded to that version. The whole point of semantic versioning is to allow you or package managers you use to limit which libraries to update. So, semver is to let you know of braking changes exactly before they would happen, because until you actually upgrade the library, the change hasn't happened. Surely this makes sense? Maybe we are talking past each other.

[ Parent | on HN ]