3 ms·
> If you use terms in an unexpected way, it will create a barrier making it harder or outright prevent you from influencing others and will likely add unnecessa
by lmm 5y ago
> If you use terms in an unexpected way, it will create a barrier making it harder or outright prevent you from influencing others and will likely add unnecessary frustration to all involved. We need to consider not just the literal meaning of a word, or its denotation, but also its connotation.
> I believe the author was intending to say that some crate authors are not adhering to 100% of the semver spec.
Article is being disingenuous here. The original author absolutely intended to call this a violation of the semver spec, with all of the connotations that brings. And frankly they're right: by "not adhering to" the spec, you break their expectations and break their builds.
> With this continuous release model, what value am I providing users by bumping minor on all API additions? Most API additions end up being small and drawing attention to them with a minor release creates just as much noise for the user to sift through as patch releases.
The rest of the article answers that: if you bump minor on all API additions, you allow others to specify a caret version with a minor version number, as the spec says they should be able to.
Either follow the damn spec, or make it very clear that you're not following the spec so that we know not to use your libraries. Certainly don't try to blame other people for being rightly annoyed that you've made more work for them by violating the spec for the sake of what seems to be essentially your personal aesthetics.
- epage 5y ago> Article is being disingenuous here. The original author absolutely intended to call this a violation of the semver spec, with all of the connotations that brings. This is assuming intent that wasn't there. At the time, I did not know the author's view was so extreme that they view bumping patch on api additions is equivelant to bumping minor on api removals. I was giving the author the benefit of the doubt. I still feel discussing whether the same language for describing both is appropriate as I assume there are enough of us unaware or that don't care about the patch handling that it it is misleading to equate them. > The rest of the article answers that: if you bump minor on all API additions, you allow others to specify a caret version with a minor version number, as the spec says they should be able to. The spec says nothing of version requirements. If you are trying to say "you can accept any patch", thats not true. The semver spec says you can add functionality so long as the API is unchanged. This is setting aside relying on bug fixes which is frequent enough.