search

k8snetworkplumbingwg / sriov-network-operator

Operator for provisioning and configuring SR-IOV CNI plugin and device plugin
Apache License 2.0
76 stars 106 forks source link

Add version tags to the containers, instead of just being linked to a commit #185

Open oreillymj opened 2 years ago

oreillymj commented 2 years ago

Can each container be associated with a release? Or at least make a quarterly release which is then accompanied by a tagged "stable" container which is similarly tagged.

On the main page, there is only 1 release, but many containers.

It therefore hard to know when you pull a container, what the changelog is and difficult to manage from a change control perspective.

Ideally every container here https://github.com/k8snetworkplumbingwg/sriov-network-operator/pkgs/container/sriov-network-operator

Has a matching release here

https://github.com/k8snetworkplumbingwg/sriov-network-operator/releases

But as backup a quarterly release strategy could be adopted with interim containers left with just commit tags.

adrianchiris commented 2 years ago

Hi,

I have created an issue to define a release process #186

for each release we should mention in release notes the tagged versions of our containers

adrianchiris commented 2 years ago

There are now tagged containers for v1.1.0 release. each release will have tagged containers for that release and mentioned in the release notes.

@oreillymj, I believe this addresses your request. can this be closed ?