These processes and SLAs are subject to change at the maintainer's discretion.
The goal of this page is to create clarity with the open-source community about what SLA's we are committing to and what triage process we are aiming to follow.
NOTE: We are starting to use the GitHub Project View to track progress of bugs that we are actively working on. Labels are still going to be used for triaging and labels to help the community track it, but for the internal development standpoint, we will prioritize the Project View.
SLA for triaging of a newly created issue
- 4 business days
- Weekends are not included. Responses are not expected on the weekends or during holidays.
State of issues after a triage pass
- The
triagelabel will be removed. A descriptor label such as "bug", "enhancement", and/or a state label will be added. - The issue will have at least one label attached along with a Microsoft response.
State labels
- triage
- more info needed
- repro needed
- investigation needed
- in progress
- fixed (release pending)
- help wanted
- more votes needed
- stale
Descriptions of the labels can be found here.
Label State Diagram
The above labels and SLA's help formulate the following state diagram that will be followed for labeling and handling of issues:
Milestone State Diagram
Additionally, we use Milestones to help us track our work and when we will be working on certain issues. The following state diagrams is used in symphony with the Label state diagram from above: