18 Triage Process

Chris Glein редактировал(а) эту страницу 2023-11-01 18:25:01 -07:00

Содержание

• Assignee
• Milestone
• Triage Process
• Goals
• Process
• Triage queries
• Triage Boards
• Bot Rules

Assignee

If an issue is assigned to someone it is assumed that that person is currently working on that issue, they plan to in the next couple weeks, or they have the next "action" on that issue. In short:

"I'm working on this", or "I want to be prominently displayed as the point of contact for this, and if anyone else wants to work on it they should talk to me first".

Contact the current assignee before working on an issue to prevent duplicated effort. If you are no longer working on one of your assigned issues you should unassign yourself (leave a note so that the next person can pick up where you left off).

To find issues assigned to you across all your repros, visit here.

Milestone

The milestone field communicates when an issue will be fixed and what release that fix is associated with.

• Release (X.XX): The issue must be fixed before that release (is:open), or that the fix has already been made for that release (is:closed)
• Next: Someone is working on this or intends to work on it soon (e.g. in the next few weeks) but the fix isn't required for a specific release
• Backlog: The issue has been triaged but isn't yet on anyone's near and upcoming workload.
• Unassigned: The issue has not been triaged

Triage Process

Goals

What are our goals for triaging incoming issues?

1. Groom a backlog of actionable issues
2. Engage with the community and respond to feedback
3. Make connections between efforts/engineers
4. Grow knowledge that spans the entire product (bring teams together) and related products (macOS etc.)

We also do our best to align with issue management practices from Facebook's react-native repo (and we participate in both) so that people have a consistent experience moving between RN and RNW.

Process

For every issue labeled Needs Triage we apply this process:

Note: Unless operating as part of the team triage meeting, please do not remove the Needs Triage label yourself.

1. Is the issue unclear?
   • Didn't specify version/environment information? Needs: Environment Info
   • On an older version? Needs: Verify on Latest Version
   • A general Windows question? Resolution: For Stack Overflow (this will close the issue)
   • Need other fundamental information?
     • @ mention the author and ask clarifying questions
     • Add Needs: Author Feedback label (these will return as Needs: Attention)
2. Labels
   • What is the category of issue?
     • bug | enhancement
     • Failing to assign one of these will trigger the Invalid Triage condition
   • Assign at least one Area (e.g. Area: Animation)
   • Is this a partner request? Partner: AppConsult, Partner: Office, Partner: Stream, Partner: Xbox, or Partner: 3P (for all others)
   • Priority:
     • Required for current release? Assign to that release's milestone
       • Consider for the next release? Assign to the Next milestone
     • Low? Label nice-to-have, Backlog milestone or close as Not Planned
     • Normal? Backlog milestone
   • Community interaction labels
     • good first issue
     • help wanted
3. Milestone
   • All triaged issues should be assigned a milestone per the criteria defined above.
     • Release (X.XX)
     • Next
     • Backlog
   • Failing to assign a milestone will trigger the Invalid Triage condition
4. Assign
   • If someone should look at this immediately, in the next block of work (1-2 weeks), or they have the next action, assign to them
   • Leave unassigned otherwise
5. Remove Needs Triage label

Triage queries

1. Needs Triage
2. Needs Attention.
3. Samples repo Needs Triage
4. Samples repo Needs Attention
5. Gallery repo Needs Triage
6. react-native-xaml repo Needs Triage
7. Dualscreen repo Needs Triage
8. Unanswered Discussions
9. Open PRs
10. Look for issues on supported community modules

Triage Boards

There are GitHub project boards to better facilitate going between the different repo queries, but are locked down to organizational access for the moment. If you have access to that organization's progress boards, you can instead use these links (which should have the same content):

1. Needs Triage
2. Needs Attention
3. Needs Answer
4. PR Triage

Bot Rules

• All new issues are labeled Needs Triage.
• If an issue with Needs: Author Feedback receives a comment from the author it changes to Needs: Attention.
• Issues without activity for 7 days with Needs: Author Feedback (or PRs with 'Changes Requested') receive a warning and are labeled no-recent-activity.
  • These will be closed after 14 days.
  • On any activity no-recent-activity is removed
• Issues labeled Needs: Environment Info will get a response with steps for how to add environment information and will be labeled Needs: Author Feedback.
• Issues labeled Needs: Verify on Latest Version will get a response with information on version compatibility and will be labeled Needs: Author Feedback.
• Issues labeled Resolution: For Stack Overflow will get a response with a redirection link and will be closed.
• PRs labeled AutoMerge will be merged if all checks are met (minimum 60 minutes opened, squash merge, deletes branch).
• Issues that do not have Needs Triage|Attention|Author Feedback and also are not labeled bug|enhancement|question, or are not placed into a milestone, are labeled Invalid Triage