Triage and Review Process: Our Commitment #7778
Description
We value community feedback and contributions to the desktop client. Your input is essential to improving the product, and we strive to interact and provide feedback in a timely manner.
Steps:
- The label 0. Needs triage is automatically added when the issue is created.
- When the issue is not clear, we need to ask questions, logs, steps to reproduce it.
- Once we request the missing information, the 0. Needs triage label is removed and needs info is added.
- The needs info label is removed automatically once the issue is updated again by the community.
- The person responsible for doing triage on the day will assign themselves to the ticket until the triaging process is completed: all necessary information is collected to confirm the bug or feature request.
- The 1. to develop label is added: the issue is confirmed and can be worked on by anyone.
Tip
We also use the label good first issue to help newcomers to get familiar with the project.
Our targets:
- Bug Reports: Review and triage within 2 weeks.
- Pull Requests: Merge within 2 weeks.
Please note:
- These are targets, not guarantees.
- Topics that do not align with the product roadmap or strategy may not be merged.
We appreciate your understanding and continued support!