22< html >
33 < head >
44 < meta charset ="utf-8 ">
5- < title > Ubiquity.NET.Versioning | Ubiquity.NET </ title >
5+ < title > Ubiquity.NET.Versioning | Ubiquity.NET.Versioning </ title >
66 < meta name ="viewport " content ="width=device-width, initial-scale=1.0 ">
7- < meta name ="title " content ="Ubiquity.NET.Versioning | Ubiquity.NET ">
7+ < meta name ="title " content ="Ubiquity.NET.Versioning | Ubiquity.NET.Versioning ">
88
99
1010 < link rel ="icon " href ="favicon.ico ">
@@ -72,7 +72,6 @@ <h1 id="ubiquitynetversioning">Ubiquity.NET.Versioning</h1>
7272but the primary focus is automated build versioning that embraces the principal of least surprise
7373while conforming to the syntax of CSemVer and CSemVer-CI</ p >
7474< h2 id ="the-libraries-in-this-repository "> The Libraries in this repository</ h2 >
75- < p > (At least the ones generating docs at this point anyway! 😁)</ p >
7675< table >
7776< thead >
7877< tr >
@@ -91,6 +90,20 @@ <h2 id="the-libraries-in-this-repository">The Libraries in this repository</h2>
9190</ tr >
9291</ tbody >
9392</ table >
93+ < div class ="IMPORTANT ">
94+ < h5 > Important</ h5 >
95+ < p > There is confusion on the ordering of a CI build with relation to a release build with
96+ CSemVer-CI. A CI Build is either an initial build of an unreleased version with
97+ [Major.Minor.Patch] == [0.0.0]. Or, it is based on the previously released version and
98+ is [Major.Minor.Patch+1]. That is, a CI build is ordered < em > < strong > BEFORE</ strong > </ em > all release builds,
99+ or it is ordered < em > < strong > AFTER</ strong > </ em > the < em > < strong > specific</ strong > </ em > release it is based on! In particular a
100+ CI build version does < em > < strong > NOT</ strong > </ em > indicate what it will become when it is finally released,
101+ but what release it was based on (If any). To simplify that, for clarity, a CI build
102+ contains everything in the release it was based on and additional changes (that might
103+ remove things). CI builds are, by definition NOT stable and consumers cannot rely on
104+ them for predictions of future stability. A given CI build may even represent an
105+ abandoned approach that never becomes a release!</ p >
106+ </ div >
94107< hr >
95108< p > < a href ="Attributions.html "> Attributions</ a > </ p >
96109
0 commit comments