I think semver could use a marker for "breaking change to a clearly marked private API that we nonetheless believe people use"
-
Show this thread
-
Replying to @wycats
Related problem with semver is how do you mark fixing a bug that has the potential to break because people are relying on the buggy behavior
4 replies 0 retweets 22 likes -
Bug fixes can go in patch versions. If possible I usually like to deprecate until the next major if I know people are relying on it.
1 reply 0 retweets 0 likes -
It's not always possible and good to call out anyway even if "bugfix"
1 reply 0 retweets 0 likes
Agreed. I always have a section for them at the top of the changelog if present
4:51 PM - 12 Oct 2017
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.