Issues Triaging

Triaging an issue is a multi-step process that is collaboratively performed by the Windows Forms team and our issue bot. The team runs several different triages based on an issue type. For example, the runtime and designer issues are generally triaged on a weekly cadence, and API proposals are triaged on a fortnightly cadence. However, some issues or proposals may take longer to triage, for example, when the feature area owner is not around. Goal of triaging is to set expectation of what will happen to your issue. For example, after your feature request was triaged, you know whether the team plans to tackle the issue, or whether the issue is best tackled by the community.

Requesting Information

If an issue lacks information that we need to understand the issue, we assign the ":mailbox_with_no_mail: waiting-author-feedback" label. The bot is monitoring all issues labeled ":mailbox_with_no_mail: waiting-author-feedback". If we don't receive the needed information within 14 days, the bot will add another label - ":zzz: no-recent-activity". If another 7 days pass without the feedback, the bot closes the issue.

Categorizing Issues

Labels are used quite extensively in the repo. Some labels represent areas of functionality, some - act as markers of business flows, and some act as indicators to the team and the community about the state of an issue or a pull-request. For example, the most common you likely encounter:

Label	Description
📭 waiting-author-feedback	There is a missing information or there are unanswered questions
waiting-on-team	There are questions to or outstanding actions that are waiting for the team's input
waiting-review	The issue or pull-request is waiting for the team's review
🪲 bug	The issue is recognized as a bug
enhancement	Product code improvement that does NOT require public API changes/additions
up-for-grabs	Good issue for external contributors
good first issue	Issue should be easy to implement, good for first-time contributors
ready-to-merge	Pull-request has been reviewed by one of the team members, but expects more reviews from the team
api-suggestion	Early API idea and discussion, it is NOT ready for implementation
api-ready-for-review	The proposed API was reviewed by the team, and it is sent to the API Review Board
api-approved	API was approved, it can be implemented
servicing-consider	The fix is deemed as meeting the servicing requirements, and presented to the servicing committee
servicing-approved	The fix is approved by the servicing committee for servicing