Document issue triage labels #3990
Conversation
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
|
This process is still be trialled by the GC so I it's still applicable. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
I believe this is ready for review. Not much has changed but we've been using this process for a while without issue now. It can be extended in the future as we refine the process. |
|
@dyladan this PR seems to focus on the definition of the roles and tags, it doesn't cover how the state machine would work - e.g. the diagram in this issue description #3821. Do you intend to make this a complete PR by adding the state machine or keeping it small? If the answer is the latter, consider updating the PR title and description. |
|
Should this also contain a note about staleness/issues aging out? |
Since we haven't developed a policy for that and this is already months old i'd rather merge what we have an iterate on it |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
|
Anything preventing this from being merged? I will merge this by tomorrow EOD otherwise (to give a last chance to review). |
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Relates to #3821
The GC is currently working on a new process for triaging and prioritizing the specification issue backlog. This document outlines the process and the labels currently being used.