You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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).
The text was updated successfully, but these errors were encountered:
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
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:
release-x.y
branch) will have a CI job that creates a draft update PR and proxies their CI status (or similar behaviour).The text was updated successfully, but these errors were encountered: