Discussion: Changeing the container tags

[rwaffen]

Hi 🙋

I’d like to discuss the build-up of container tags. As they currently stand, they seem to be difficult to use. Therefore, I propose that we make some changes.

# now
#
8.14.1-v1.2.3
8.14.1-main

# proposal
#
8.14.1-2

We primarily pin it to the software that is mainly bundled into the container. Therefore, the container version is identical to the openvoxserver version. Additionally, there is a -<Number> like in rpm packages, where the counter increments whenever there are changes in the packaging, but not the software itself.

Whatcha thinking about that?

[JGodin-C2C]

on the idea of using a number for the container as well, i totally agree.
However, i think using "packaging change" is not a good idea .

Why ?
The tag should indicate the build that created the image (Where does this image comes from ?).
This involve two things : the commit and the build date.
We do not need to always use the full tag, but something like this :

openvoxserver:[openvoxversion]-[branch]-[commitid]-[date]

This will allows us to test new versions and absolutly pin-point the build the image comes from. This helps for debugging for instance , old builds with faulty dependencies.

In addition, a signature would be great for good-measure but not a must.