Ubiquity.NET.Versioning
Ubiquity.NET.Versioning* family of libraries provides support for a number of scenarios
but the primary focus is automated build versioning that embraces the principal of least surprise
while conforming to the syntax of CSemVer and CSemVer-CI
The Libraries in this repository
| Library | Description |
|---|---|
| Ubiquity.NET.Versioning | This library contains support for use of CSemVer at runtime |
Important
There is confusion on the ordering of a CI build with relation to a release build with CSemVer-CI. A CI Build is either an initial build of an unreleased version with [Major.Minor.Patch] == [0.0.0]. Or, it is based on the previously released version and is [Major.Minor.Patch+1]. That is, a CI build is ordered BEFORE all release builds, or it is ordered AFTER the specific release it is based on! In particular a CI build version does NOT indicate what it will become when it is finally released, but what release it was based on (If any).
To simplify that, for clarity, a CI build contains everything in the release it was based on and additional changes (that might remove things). CI builds are, by definition, NOT stable1 and consumers cannot rely on them for predictions of future stability. A given CI build may even represent an abandoned approach that never becomes a release!
1 Stability, in this context, refers ONLY to consistency of the specified behavior and the APIs used to access it in relation to that of previous releases. The term, as used here, has NO relation to the concept of the quality of the implementation.