A short note on how protocol Releases are numbered and why exactly this way.
Patch only
Version grows in the third number. Jumps through minor and major are possible only by a separate, explicit decision of the human.
In tens, not in units
After 0.4.5 goes not 0.4.6, but 0.4.51, then 0.4.52 and so on. Technically this is not needed. The choice is deliberate: so that the number, with frequent small fixes, does not look like “we have only just started.”
Commit and version are different things
A commit is a unit of history and rollback, so commits happen often: each card is committed as work proceeds. The version is raised once per release, and only when something has changed for the consumer: a new file, a changed rule, a fixed behavior.
Version does not go backward
The update check compares “strictly newer”, so rolling back the number silently hides a release. There was a precedent: an edit brought back the whole file together with the old number, and this was noticed only several versions later.
The comparison is numeric
0.4.9 < 0.4.51 < 0.4.100 < 0.5.1: the number of digits can grow freely.
Comments