---
# System prepended metadata

title: Issue Triage Proposal
tags: [community]

---

---
tags: community
---
# Issue Triage Proposal

## GitHub issue flow

1. Issue is opened, reopened, or closed and has a new comment
    * the issue is labeled with **carvel-triage** to let maintainers know it requires review.


2. Triage
    * A maintainer researches and discusses the issue and documents reproduction steps or UX. One of the following labels is applied 
        * **enhancement** - The issue is a feature request.
        * **bug** - The issue is defect or unexpected behavior.
        * **good first issue** - An issue that will be a good candidate for a new contributor. 
        * **discussion** - The issue is not a bug or feature and a conversation is needed to set forth an appropriate resolution. 
        * **helping-with-an-issue** - Debugging happening to identify the problem
        * **duplicate** - The issue is already captured by another issue.
        * **documentation** - This label indicates a change to the docs should be considered.

    * Once all relevant information has been collected and documented in the issue, and a maintainer has made a decsion on whether we will move forward with the issue, the **carvel-triage** label is removed.
        * If the issue will be considered further, the **carvel-accepted** label will be added to indicate the issue should be considered for future work and that the triage process has been completed.
    * If we are unable to get enough information and an issue has the **carvel-triage** label and no activity for more than 45 days it will be closed. Note: this excludes issues labeled as discussions.

3. Planning
    * The goal of planning is to figure out how, if at all, to act on the issue. An issue may be in this stage for any amount of time.

4. In-progress
    * The in progress stage begins when someone begins work on the issue. A maintainer adds the  **in-progress** label to indicate work is currently happening by a community member or a maintainer, and the issue may be included in a future release.
 
5. Closed
    * If at any point in the lifecycle stages an issue is closed, it is an indication that the issue was resolved and requires no further action from the community role. An issue author can reopen the issue at any time if they feel it has not been resolved.
        * If a new comment is added to a closed issue, the **carvel-triage** label will be added to let a triager know it should be looked at.
