Bug
How we deal with bugs
Steps
- If the issue is a bug, make sure to recognize the user who made the PR as a #role.bugcatcher (Private) by following the process in community highlights (Private)
- If the bug is low priority, mark it as such and skip to the last step
- NOTE: a bug is low priority if it happens in very rare edge cases and would take much effort to repro. ping
#team-chat
if not sure
- NOTE: a bug is low priority if it happens in very rare edge cases and would take much effort to repro. ping
- Assign an owner from the team (can be the current oncall or the person who has worked on the feature last).
- NOTE: if you are confused at this step, ping inside
#team-chat
to figure out the owner
- NOTE: if you are confused at this step, ping inside
- If the bug high priority, mark it as such
- NOTE: as of today, high priority means it impacts a lot of users - use your best judgement for this and ping in
#team-chat
if you're not sure, we're working on coming up with better metrics around this - some heuristics around high priority:
- anything to do with common publishing operations
- anything that pertains to Core Features Maturity (Private)
- NOTE: as of today, high priority means it impacts a lot of users - use your best judgement for this and ping in
- Export the task note
Notes
At the start of the next sprint, we'll make sure to prioritize bug fixes
Backlinks