You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: