Update triage to include release instructions #22335
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After chatting with @aduth about release specific triage processes, I wanted to pull together insights he shared around how to approach adding milestones, flagging bugs for the team, etc. Adding this in as an update to these instructions.
aduth
approved these changes
May 13, 2020
Co-authored-by: Andrew Duthie <andrew@andrewduthie.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After chatting with @aduth about release specific triage processes, I wanted to pull together insights he shared around how to approach adding milestones, flagging bugs for the team, etc. Adding this in as an update to these instructions. This should help anyone doing triage better know how to escalate bugs to the team and what bugs should be escalated in general.