Release plan / Release 1.26.4 / 1.27.1 #7114
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
I agree that it would be beneficial to note the release timing in the documentation for better visibility and knowledge. CRI-O typically releases its latest version within one or two weeks after the release of Kubernetes. I think the minor version releases are a bit ad-hoc and mostly focused on bug fixes. |
Beta Was this translation helpful? Give feedback.
-
|
FWIW: I have been planning a 1.27 and 1.26 one for a bit but there keep being changes I am trying to pull in. Is there a particular fix you're looking for? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for the answers. I'm waiting for the fix for issues regarding missing metrisc (#6657, #6805, etc.). The fix is already on both branches, but not yet released: #6856 |
Beta Was this translation helpful? Give feedback.
-
|
the two versions have been submitted today and should be packaged soon! thanks for your patience here |
Beta Was this translation helpful? Give feedback.
I agree that it would be beneficial to note the release timing in the documentation for better visibility and knowledge. CRI-O typically releases its latest version within one or two weeks after the release of Kubernetes. I think the minor version releases are a bit ad-hoc and mostly focused on bug fixes.