2 ms·

The moment you allow bugs, you can't ensure backwards compatible changes. That makes semver as good as any other scheme, including GitDate.

• jjav 4y ago
  > The moment you allow bugs, you can't ensure backwards compatible changes. I'm not sure what this even means, unless you're talking of the joke of "someone depended on the bug"? A bug, by its very definition, means code that doesn't behave as the documented interface description states. Fixing bugs means correcting mistakes in the code so that now it does behave as documented. That's what patch releases do.
  • k__ 4y ago
    No, but if you say you don't break API in minor, but you have a bug that breaks API, then minor broke API.
    • jjav 4y ago
      Are you referring to the possibility of a minor release introducing a bug? Yes, of course that's possible, nobody is pretending humans are infallible. When it happens, just issue a patch release to that minor release to fix the bug. Versioning is about communicating intent, it's not a guarantee that nobody can ever make a mistake. But if you're constantly introducing bugs in minor releases, that's a sign of sloppy test infrastructure and it will motivate me to migrate away from such a library. But the occasional bug is normal, fix it quick and move on.