[BetterRed]

Originally Posted by PeterT

Any thoughts on standards / techniques that could be implemented to handle these issues?

I don't have much to add, that hasn't already been said.

I don't interpret or attach any significance to version numbers, providing they are orderly. I don't like cute names. Aside: why has there never been a MacOS Esalen.

All I ask is that temporary (experimental, beta, whatever…) versions should not be left lying around in Plugin thread replies if they are superseded by an official or another temporary version. If they can't be removed by the originator for some reason they should report the offending post, or PM a calibre mod with a request they be removed.

---

Originally Posted by JimmXinu

. . .

FYI, semi-related, Github releases want Semantic Versioning (https://semver.org/) these days. Which does allow for extra specificity after the micro number, but doesn't want anything before the version number.

Curious, who 'owns' the Semantic Versioning 2.0.0 document, which has this:

As a solution to this problem [dependency hell], we propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented.

So, who is 'we'… We the people, the royal We, Zemyatin's We