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

Add documentation about how we handle incoming breakages #70

Open
guarani opened this issue Oct 11, 2021 · 0 comments
Open

Add documentation about how we handle incoming breakages #70

guarani opened this issue Oct 11, 2021 · 0 comments

Comments

@guarani
Copy link
Contributor

guarani commented Oct 11, 2021

If a release is cut and an issue is found, we might first classify the issue as a blocker or non-blocker and then we must decide whether to continue the release, revert the offending commit (if we've located it e.g. via git bisect), or pause the release while a fix is found.

It would be useful to capture these three scenarios in the documentation so that we have some established guidelines for how to proceed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant