Clarifying Our Triage Process with the needs-area-owner-attention Label

[Lauren Ciha (lauren-ciha)]

Hello Windows App SDK community,

We've heard your feedback that we can make our triage process clearer. We wanted to share a new label that helps clarify what an issue needs next.

New needs-area-owner-attention label

Before, we used needs-triage to mean two different things. For issues without an area label, it meant that the issue needed to be routed to the owning team. Once an issue was routed to an area, needs-triage meant that the issue needed review from the owning team.

We've heard you ask us to separate those meanings into two labels, so we're introducing needs-area-owner-attention. Going forward, needs-triage means that the issue needs to be routed to the owning team for its feature area. Once the owning team has been identified, needs-triage will be replaced with needs-area-owner-attention to indicate that the issue needs review from the feature area team.

The triage process

An issue is opened and receives the needs-triage label so the maintainers can route the issue to the owning team.

Issues are reviewed to identify their feature area about twice per week. When the owning area has been identified, the team will add an area label, remove needs-triage label and add needs-area-owner-attention to indicate that the issue needs review from the feature team.

For filers, the change from needs-triage to needs-area-owner-attention is the visible sign that the issue has been routed to its owning team. Please follow the issue for updates or requests for more information.

[whiskhub]

Nice!