Where we feel that back-porting would be difficult or might be a stability #3444 is an example of a long-standing bug. Long-standing bug: sometimes a bug exists for a long time, and may have Patch release for the currently supported releases. Note that intentional breaking changes do not belong toįixes for critical bugs are (usually) immediately back-ported by creating a new #3882 and #3644 are examples of upgrade bugs. Upgrading to currently supported releases from earlier releases ofĬert-manager. Upgrade bugs are issues (often Helm-related) preventing users from #4142, #3393 and #2857 are three examples of regressions. Regressions are functionalities that worked in a previous release but no longer Critical bugsĬritical bugs include both regression bugs as well as upgrade bugs. The last two releases, and a new patch release is immediately created for them. Security issues are fixed as soon as possible. We back-port important bug fixes - including security fixes - to all GitHub Discussions or using the cert-manager-dev Slack (in the #cert-manager channel), using You can request support from the community on Kubernetes Technical assistance is offered on a best-effort basis for supported We offer two types of support:įor example, imagining that the latest release is v1.2.0, you can expect Window corresponds to the two latest releases, given that we produce a newįinal release every two months. In the belowĭiagram, release-1.2 is an example of a release branch.
Our support window is four months for each release branch. We also maintain detailed upgrade instructions.
Currently supported releases Releaseĭates in the future are uncertain and might change. Release roughly every two months, accounting for holiday periods, major conferencesĪnd other world events. This page lists the status, timeline and policy for currently supported releases.Įach release is supported for a period of four months, and we aim to create a new
0 kommentar(er)
