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 process]: Require the release compatibility with big user e.g. Kubernetes #1648

Open
bwplotka opened this issue Oct 15, 2024 · 0 comments

Comments

@bwplotka
Copy link
Member

The idea is to learn about any surprising breaking change and have data to make decision if we should revert or accept the breakage (and ping/help downstream users) -- ideally as an automated CI check on every PR to the release branch.

Some repos we could try setting this up against:

Acceptance Criteria:

  • Every release PR (e.g. against release-x.y branch) will have a CI job that creates a draft update PR and proxies their CI status (or similar behaviour).
@bwplotka bwplotka changed the title Release process: Require the release compatibility with big user e.g. Kubernetes [release process]: Require the release compatibility with big user e.g. Kubernetes Oct 15, 2024
@dosubot dosubot bot added the chore label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant