1616
1717
1818
19- < meta name ="docfx:docurl " content ="https://github.com/UbiquityDotNET/CSemVer.GitBuild /blob/develop/docfx/index.md/#L1 ">
19+ < meta name ="docfx:docurl " content ="https://github.com/UbiquityDotNET/Ubiquity.NET.Versioning /blob/develop/docfx/index.md/#L1 ">
2020 < meta name ="loc:inThisArticle " content ="In this article ">
2121 < meta name ="loc:searchResultsCount " content ="{count} results for "{query}" ">
2222 < meta name ="loc:searchNoResults " content ="No results for "{query}" ">
@@ -84,10 +84,6 @@ <h2 id="the-libraries-in-this-repository">The Libraries in this repository</h2>
8484< td > < a href ="versioning-lib/index.html "> Ubiquity.NET.Versioning</ a > </ td >
8585< td > This library contains support for use of CSemVer at runtime</ td >
8686</ tr >
87- < tr >
88- < td > < a href ="build-tasks/index.html "> Ubiquity.NET.Versioning.Build.Tasks</ a > </ td >
89- < td > This library contains support for automated versioning at BUILD time</ td >
90- </ tr >
9187</ tbody >
9288</ table >
9389< div class ="IMPORTANT ">
@@ -98,19 +94,23 @@ <h5>Important</h5>
9894is [Major.Minor.Patch+1]. That is, a CI build is ordered < em > < strong > BEFORE</ strong > </ em > all release builds,
9995or it is ordered < em > < strong > AFTER</ strong > </ em > the < em > < strong > specific</ strong > </ em > release it is based on! In particular a
10096CI 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 >
97+ but what release it was based on (If any).</ p >
98+ < p > To simplify that, for clarity, a CI build contains everything in the release it was based
99+ on and additional changes (that might remove things). CI builds are, by definition, < em > < strong > NOT
100+ stable < sup > < a href =" #footnote_1 " > 1 </ a > </ sup > </ strong > </ em > and consumers cannot rely on them for predictions of future stability. A given CI
101+ build may even represent an abandoned approach that never becomes a release!</ p >
106102</ div >
107103< hr >
108104< p > < a href ="Attributions.html "> Attributions</ a > </ p >
105+ < p > < sup > < a id ="footnote_1 "> 1</ a > </ sup > Stability, in this context, refers ONLY to consistency of
106+ the < em > < strong > specified</ strong > </ em > behavior and the APIs used to access it in relation to that of previous
107+ releases. The term, as used here, has NO relation to the concept of the < em > < strong > quality</ strong > </ em > of the
108+ implementation.</ p >
109109
110110</ article >
111111
112112 < div class ="contribution d-print-none ">
113- < a href ="https://github.com/UbiquityDotNET/CSemVer.GitBuild /blob/develop/docfx/index.md/#L1 " class ="edit-link "> Edit this page</ a >
113+ < a href ="https://github.com/UbiquityDotNET/Ubiquity.NET.Versioning /blob/develop/docfx/index.md/#L1 " class ="edit-link "> Edit this page</ a >
114114 </ div >
115115
116116 < div class ="next-article d-print-none border-top " id ="nextArticle "> </ div >
0 commit comments