Does cape's versioning follow any scheme?

[hab25]

@minad, further, will the answer be the same when referring to all of your other Emacs packages?

---

PS:

I noticed it does not follow semantic versioning (semver) because it made (at least) one incompatible API change in version 2.1 (i.e., cape-dabbrev-check-other-buffers: Removed in favor of cape-dabbrev-buffer-function.). Following semver, this version would have been numbered with major version 3 (e.g., "3.0" or "3.0.0").

A versioning scheme that conveys breaking changes is useful: it helps users that rely only on documented behavior save time reviewing changelogs in situations where they don't care about new features, but care about correctness and performance improvements.

[minad]

No, my packages do not follow semantic versioning. I do see your point but I don't like that semantic versioning raises the major version much too quickly. For my packages the major version roughly reflects the maturity of the package, but this is of course rather fuzzy.