Image tagging convention

[erkannt]

Some things we have noticed during validation of this ADR proposal using the reviewer project. Mostly clarifications.

[erkannt]

From trying to track uploaded images in the compose files of libero/reviewer I'm learning that hash-based versions are tricky. At least for renovatebot, which unlike dependabot can handle compose files and helm charts.

The original hope was to use their regex versioner to match our branch-hash tags. Sadly the regex versioner needs to have at least one match group that corresponds to a numeric major, minor or patch value.

Solutions might be:

• abandon the tracking of branch-hash images and switch everything to semver ASAP
• extend the tags to branch-hash-timestamp, feed timestamp into patch and branch into compatibility
• make our own versioner and open a PR with renovatebot (they use ts, see example)

Our tagging scheme isn't the only one affected. Minio stable releases are simply tagged latest and their daily releases are tagged RELEASE.2020-04-02T21-34-49Z. I so far also haven't found a way to sensibly track these. But here the issue is less critical as latest is less likely to break things.

[giorgiosironi]

Discussed in Libero sync to be approved and reversed if it proves problematic.