4 ms·

I now prefer ComVer, "Compatible Versioning" [1][2] [1] https://gitlab.com/staltz/comver https://gitlab.com/staltz/comver [2] https://staltz.com/i-wont-use-se

• cpeterso 6y ago
  Thanks! I've been hunting for this blog post, but couldn't remember the name "ComVer". I was hoping someone in this HN thread would mention this. :)
• smichel17 6y ago
  May I suggest my own invention, smver? It's MajorPatch.Minor, where Patch is lettered. For example, this spec itself, which I wrote today, is at v0a.1. The first stable version will be 1a.0. Basically, it's the same principle as comver, where any breaking change must increment the first identifier, but with some added metadata to hint how big of a change the developer intended this to be. You can omit the patch if you want, in release announcements, so marketing can have the "6.0 released!" moment (I am considering omitting the patch letter for the first major release, so 4a.0 follows 4.0).