build: add explicit commit to rc1, rc2 builds, and add ".0" to post-non-dot-release... 82/27782/4
authorAndrew Yourtchenko <ayourtch@gmail.com>
Thu, 2 Jul 2020 12:39:00 +0000 (12:39 +0000)
committerDamjan Marion <dmarion@me.com>
Tue, 18 Aug 2020 10:40:15 +0000 (10:40 +0000)
commit1060332e62d1216bf33c697d0a54ba35d4903eb3
tree7c56a437d18492074386a979a1e14e88a3e2b13f
parent42b29ba3d4a30e4bf660f3a0a6a4af40d62861fe
build: add explicit commit to rc1, rc2 builds, and add ".0" to post-non-dot-release per-patch builds

This addresses problem with incorrect sorting of artifacts in the per-patch packagecloud repositories
for throttle branches, by slightly changing the version string for the non-released (per-build) artifacts:

1) the rc1 and rc2 artifacts now will have the count of
   commits since tag (0) and the explicit commit hash

2) the builds after version XX.YY but before XX.YY.1
are named as if the version was "XX.YY.0"

Type: fix
Change-Id: Ib69a59ee98aa296c5cb24b183bba807b6cb3c05c
Signed-off-by: Andrew Yourtchenko <ayourtch@gmail.com>
src/scripts/version