XXIIVV — kelvin versioning

Software versioning in which a version is an integer in degrees Kelvin.

In short, a supporting component must always be strictly cooler than anything<br>it supports, or be at absolute zero conjointly with anything it supports.<br>Absolute zero means that a program is frozen , no further updates are<br>possible. If your versions don't track your<br>actual progress, you run out of integers.

DependenciesVersions<br>A9K<br>B19K<br>C20K<br>D28K

If tool B sits on platform A, either both A and B must be at absolute zero, or<br>B must be warmer than A. Whenever the temperature of platform A declines,<br>the temperature of tool B must also decline. Of course, if B itself is a<br>platform on which some higher-level tool C depends, it must follow the same<br>constraints recursively.

A's version SHALL be a nonnegative integer.

A, at any specific version, MUST NOT be modified after release.

At version 0, new versions of A MUST NOT be released.

New releases of A MUST be assigned a new version, and this version MUST be strictly less than the previous one.

If A supports another component B that also follows kelvin versioning, then:

Either both A and B MUST be at version 0, or B's version MUST be<br>strictly greater than A's version.

If a new version of A is released and that version supports B, then a new<br>version of B MUST be released.

Reference

0K: Theoretical minimum energy.

2K: Triple of helium.

13K: Triple point of hydrogen.

54K: Triple point of oxygen.

77K: Boiling point of Nitrogen

234K: Triple point of Mercury.

273K: Freezing point of water

273K: Triple point of water

373K: Boiling point of water

4000K: Sublimation of carbon

incoming: uxntal software varvara about now lie in it collapse computing