3 ms·

Interesting 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 f

by gitgud 5y ago

Interesting 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 ago
It 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.