4 ms·
I was dissatisfied with SemVer and it turns out that most people are using it wrong. So, I created ChronVer[0] (Chronologic Versioning). There's a JS/Node plugi
by NetOpWibby 5y ago
I was dissatisfied with SemVer and it turns out that most people are using it wrong. So, I created ChronVer[0] (Chronologic Versioning). There's a JS/Node plugin I made that will automatically increment your package.json version, and someone else made a Rust crate!
[0]: https://chronver.org https://chronver.org
- gitgud 5y agoInteresting idea but it's probably only suited to end users of applications, not for npm libraries as the landing page proposes. The reason sem-ver is better for libraries is that it indicates the compatibility of different version's API's. It doesn't matter when the version was released, just if it has breaking changes, or is just a patch release. Sem-ver is the simplest solution to this problem.
- NetOpWibby 5y agoIt works for me. For people on large teams or orgs, this merging of SemVer and ChronVer would probably be best: https://twitter.com/grin_io/status/1390747474780901380 https://twitter.com/grin_io/status/1390747474780901380 I may replace the branching model I have in the current spec with this.