Hi all, Over the time, users have complained a few times during the various release stages that the "latest at that time" version does not fetch from the throttle packagecloud.io repositories.
I have investigated the issue, and turns out the way we tag the versions is not very friendly to the way various deb utilities are doing the sorting. The visible effect is that the build that has the rc2 label on is considered older than the builds between rc1 and rc2, and also the builds between the initial release and .1 release are considered even older than rc1 and rc2 builds. The long analysis is here: https://gist.github.com/ayourtch/898ca949d640a3a4cc1bcede74f0924e I would like to make the change as per: https://gerrit.fd.io/r/c/vpp/+/27782 It boils down to: 1) add the .0 to the per-build artifacts after the initial release but before the .1 release 2) add the full "git describe" string to rc0 - rc1 - rc2 builds that have the label on. So I would like to get the community notified about that - as well as to collect any feedback you have. Notice that end-to-end sort order is still incorrect, but that in my experiments would require a bigger tweaking of artifact versioning, which given that noone reported as a problem, seems unnecessary. Thoughts ? --a
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16883): https://lists.fd.io/g/vpp-dev/message/16883 Mute This Topic: https://lists.fd.io/mt/75276044/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
