Staying in Sync: How We Follow Up on Issues

[lauren-ciha]

Hi Windows App SDK Community,

We want to clarify how we manage issues over time, especially what to expect when we need additional information from you. Clear communication helps us keep issues moving and ensures we’re focusing on the work that matters most to you.

What Our Issue Labels Mean

• needs-triage: This label means that the issue needs attention and/or triage from the community maintainers.
• needs-author-feedback: This label means that the maintainers have seen the issue and need more input from the issue author to resolve the issue.
• no-recent-activity: This label is added when we've requested feedback, but haven't received a response from the author in over a week.

The Issue Lifecycle

When an issue is opened, we triage it as quickly as possible. In some cases we may need more details to reproduce, investigate or fully understand the scenario. When this happens, you'll see the following flow:

• When someone on our team reaches out with a question or request for more details, we’ll add the needs-author-feedback label.
• If we don’t hear back after about a week, we’ll add the no-recent-activity label as a heads‑up.
• If there’s still no response after another week, the issue will automatically close to help us keep the backlog current and actionable.

What if my issue was closed?

Discussions don't have to end when an issue is closed. If you have new information or follow-up questions, feel free to leave a comment. This re-adds the needs-triage label so the issue can be reviewed again. We regularly review these comments and may reopen issues based on new findings.

Impact on the WinAppSDK Community

Staying engaged in the conversation helps us:

• Unblock investigations
• Better understand real-world impact and priorities
• Deliver improvements faster

We appreciate the time and effort the community puts into reporting issues, answering follow-up questions and sharing feedback.