3 ms·
Why do you think libraries get any releases at all? Software A and B depend on C (version V). A has a bug that gets fixed by shipping with C version V+1. B unf
by rtpg 2y ago
Why do you think libraries get any releases at all?
Software A and B depend on C (version V). A has a bug that gets fixed by shipping with C version V+1. B unfortunately has a latent bug that appears when shipping with C (version V+1).
You’re now going to have to do a bunch of work, outright not ship stuff, or even introduce bugs because of this policy!
Nobody wants buggy libraries, and in this example it’s not the library’s fault (B might just be misusing C, or in fact compensating for a bug).
Reading through these threads I’m much more empathetic to the software bill of materials argument than before as a justification for this policy. I do not think there’s an intrinsic quality argument to the global single version policy.
Bug fix releases are proof that sometimes you do really just need to put out new things to fix a bug.
- LtWorf 2y ago> Why do you think libraries get any releases at all? I mean… you're welcome to write a book and not publish it, just don't expect anyone to read it no? Same thing with libraries.