search

k3s-io / k3s-selinux

SELinux policy for k3s
Apache License 2.0
66 stars 20 forks source link

RPM versioning #49

Open bdabelow opened 1 year ago

bdabelow commented 1 year ago

As we might need to deploy a testing version due to https://github.com/k3s-io/k3s-selinux/issues/36 (via our own repos), we have a question about the exact strategy for release numbering, that is not clear to me from the README.

All the 1.2.*.2 tags are on the same commit, however 1.2.latest.1 and 1.2.testing.1 are different from each other.

Can we assume that 1.3.testing.10 will become 1.3.stable.10 (if released) and any future release in stable channel will have a higher RPM release number? Or will the first stable 1.3 release be 1.3-1 no matter what testing release it was before? The latter would mean some challenges for upgradeability when channel hopping.

I would be willing to come up with a PR to try to improve README when clarified here.

Thanks.

Klaas- commented 1 year ago

I think your question was answered by a release: https://github.com/k3s-io/k3s-selinux/releases/tag/v1.3.stable.1