This repository has been archived by the owner on May 3, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 340
Community Triage Process
VenkyOS edited this page Jan 13, 2021
·
36 revisions
TLDR; This document describes out community triage, how it works, who does it and what to expect. Questions? justin.woo@seagate.com
- If the problem has not already been resolved by someone outside the triage team.
- Acknowledge within 24 hours that we have seen the issue (excluding weekends, holidays, PTO)
- Reproduce the issue and acknowledge whether we can/cannot reproduce the issue.
- Stay on the issue until it’s closed
- If necessary, engage a member of the engineering team to help. Continue to stay on to make sure that person properly and expeditiously handles the issue. Officially, Mukul Malhotra provides L2 support for us.
- If it requires more than 4 hours of support then make sure issue is in github project-board and properly assigned and updated.
- Report summary in #cortx-community-triage
- Document it (if needed) to help the community not run into the same issue in the future
- Post a daily status (excluding weekends, holidays, PTO) in the Slack cortx-community-triage channel (even if no issues were seen).
Repo | Responsibility |
---|---|
main | Justin + Saumya (Venky for VM/OVA issues) |
motr + s3server | Patrick + Venky |
prvsnr + management-portal + manager + monitor + experiments | Justin + Mayur |
ha + hare + utils + posix | Patrick + Mayur |