Skip to content

Plans and schedule on versioning OpenVoxDB container #17

Description

@nsballmann

First of all, thank you all for taking care of PuppetOpenVoxDB and releasing it in a container.

At https://github.com/OpenVoxProject/container-openvoxdb/pkgs/container/openvoxdb#version-schema the readme describes that you plan on releasing with the following schema ${openvox.major}.${openvox.minor}.${openvox.patch}-v${container.major}.${container.minor}.${container.patch}. Are you sticking to this plan and if so, what's your schedule for that?

Because right now I'm seeing ${openvox.major}.${openvox.minor}.${openvox.patch}-latest or ${openvox.major}.${openvox.minor}.${openvox.patch}-main tagged container packages at https://github.com/OpenVoxProject/container-openvoxdb/pkgs/container/openvoxdb and that's basically preventing me from switching from ghcr.io/voxpupuli/{container-,}puppetdb to ghcr.io/openvoxproject/openvoxdb. For version pinning I would like to use comprehensive container tags, because IMHO digests work for renovate bots but not necessarily for humans.

What can I help with for the comprehensive container tag versioning to become reality?

Related to OpenVoxProject/container-openvoxserver#37

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions