Issue Lifecycle

Triaging issues is a maintainer's duty. The goal is to keep the list of open issues concise, without duplicates, stale or unclear requests. This document will explain how triaging issues work on Dapr repositories.

States

              Created
                 |
    +------------+
    |            |
    V            V
  Stale ----> Triaged ----> Sized
    |            |            |
    +------------+------------+
                 |
                 V
               Closed

Created

An issue is created by community members, it might include a label based on the template selected. For example, the bug template automatically adds the kind/bug label.

Stale

Issues that do not have any activity for a period of time (usually, 60 days) and are not triaged, will be marked with the stale label and closed after an additional 7 days of inactivity.

Triaged

An issue is considered triaged when a maintainer keeps the issue open and assigns the following labels:

• Priority: p0, p1, p2 or p3 - where a p0 is a bug that requires a patch release (hotfix) while a p2 is a nice to have. Priority p3 is optional and it simply means an even lower priority than p2 and maintainer might decide to close and add the wontfix label.
• Pinned: pinned or triaged/resolved - avoids bot to close it as stale.

Optionally, maintainer can add the following labels:

• Area: area/* - indicating which areas of the code will probably be affected.
• Complexity: good first issue - indicating an easy issue for first time contributors.

Sized

An issue is considered sized when, in addition to the triage labels, it contains any of the size/* labels, estimating the amount of work required:

size/xs size/s size/m size/l size/xl

Closed

Issues can be closed due to:

Reason	Label	Description
Staleness	stale	Issue was not triaged and did not have any activity for a long period of time.
Duplicate	duplicate	Issue is a duplicate of another issue.
Won't fix	wontfix	Issue is not aligned with the scope of Dapr project or intended use.
Done		Issue was resolved.

SLAs

Triaging bugs

Issues containing kind/bug label (via template) are expected to be triaged within 5 days.

Other issues

Other issues do not have an SLA to be triaged since some might spark healthy community discussions and maintainers should not put a deadline to those. If the issue is about a bug, then it should be prioritized as per the SLA above.

Join the #monitoring channel in our Discord server for daily updates on our SLAs: