Closed olofk closed 2 years ago
Thanks Olof! In this commit (https://github.com/grayresearch/CFU/commit/4226439e78e93cf0a9b20dac5c646c1859782a09) I renamed CFU_VERSION to CFU_LI_VERSION to clarify it defines the CFU-LI spec version, not a version of the CFU component itself. I adopted your suggestion of using semantic versioning version numbers. (I've been using those major.minor.revision in software since 1987.) I also added a new Introduction section 1.6 Versioning which is the start of a much longer discussion of versioning of the specs themselves, and specific custom interfaces, and implementations, how that works, and how it is supposed to preserve robust composition over time. Please take a look and I'd welcome more feedback and questions.
Looks great! Closing this
No rules are currently defined for when and how to increase a version. I propose we use semantic versioning (https://semver.org/) as that is relatively well understood. Technically I think we should replace the decimal
100
for version1.00
with a 24-bit vector24'hxxyyzz
where roughly xx=major version (for incompatible changes), yy=minor version (for feature additions) and zz=revision (for non-functional changes, fixes, clarifications etc)