Use a single incrementing number for versions and write a clear changelog
-
-
-
Replying to @wycats @jlongster
I want to communicate that I did not make any intentional breaking changes to documented APIs in a standard way. That's semver.
1 reply 1 retweet 0 likes -
Replying to @wycats
"intentional" is key point; too many people (and tools) use semver as if it *definitely* could not break anything, which is my problem w/it
2 replies 0 retweets 6 likes -
Replying to @jlongster
People should file bugs if I said I didn't break anything and did. But need a way to encode that.
1 reply 0 retweets 0 likes -
Replying to @wycats
Yeah, and I believe in encoding that info in a changelog which people read. It's more scalable to varying types of changes.
1 reply 0 retweets 1 like -
-
Replying to @wycats @jlongster
"intentional breaking change to a documented API" is different in kind from other changes. It deserves to be first class.
1 reply 0 retweets 3 likes -
Replying to @wycats @jlongster
It's about risk management. If I thought every meal was potentially a fugu meal, my lunches would be far more infrequent and time consuming.
2 replies 0 retweets 6 likes -
Replying to @sebmarkbage @wycats
Yeah, all good points. Perhaps I’m a little jaded from bad/religious uses of semver in the past
1 reply 0 retweets 4 likes
Religion on this front is just as bad as other fronts, but "I intended to break you" is a pretty useful thing to communicate. YMMV
-
-
I think
@jlongster will appreciate@andrestaltz's ComVer:https://github.com/staltz/comver0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.