Skip to content
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

[release-1.2] 📖 clarify backport-policy #7289

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,14 @@ The test module, clusterctl, and experiments do not provide any backward compati
#### Backporting a patch

We only accept backports of critical bugs, security issues, or bugs without easy workarounds, any
backport MUST not be breaking for either API or behavioral changes.
backport MUST not be breaking for either API or behavioral changes. In order to improve user/developer experience
maintainers can choose to backport:
- Doc improvements
- Improvements to CI signal
- Improvements to the test framework (enabling improvements to provider's test signal)
- Cert-manager bump (to avoid having branch using cert-manager versions out of support, when possible)
- Changes required to support new Kubernetes versions, when possible.

We generally do not accept PRs against older release branches.

### APIs
Expand Down