New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
releases: Shall we reevaluate the release candence for the 2.4.0 and onwards? #243
Comments
+1 to re-evaluating. Sounds like a good topic for the AC meeting. But also, we should explore the question in the user survey to get as much exposure around the question as possible. |
The form was sent out: https://forms.gle/nWM7kdcfX88Edkkt7 and http://lists.katacontainers.io/pipermail/kata-dev/2021-December/002296.html |
After pretty much 2 weeks of the form being out, we had 7 answers: 5 from the architecture committee, one from IBM, one from Red Hat. With the form we learned that:
|
From what we get from the answers the new model would be:
My suggestion here is:
I'd like to hear from @amshinde, @ariel-adam, @bergwolf, @egernst, @sameo, and @skaegi if my proposal is fair. |
During the architecture committee meeting held on Dec 14th, 2021, we agreed on following the suggestion of having minor releases every 4 months, with patch releases happening every month. The stable branch will be maintained for 4 months, and the wiki is already updated (see: https://github.com/kata-containers/community/wiki/Release-Team-Rota). I'll raise a new issue to update https://github.com/kata-containers/kata-containers/blob/main/docs/Stable-Branch-Strategy.md and I'm closing this one now. |
Thanks @fidencio ! Yep, a new table in that doc would summarise that nicely. |
During a few release cycles we experimented with a shorter cadence for our releases, which combined with the maintainence of only one stable branch, has had some impact on our users.
The current way of handling releases, as described here has made a release life-cycle reasonably short, maybe way too short for some companies taste.
Moving to a longer period could have a negative impact of waiting for too long in order to get something out, and also increasing the maintainence burden on the stable branch, but then companies could be able to rely more on the stable branches.
This, combined with a LTS proposal made some time ago could be explored for finding the right balance between what we currently have and what we may want to do.
/cc @amshinde @bergwolf @egernst @sameo @kata-containers/redhat
The text was updated successfully, but these errors were encountered: