Skip to content

Docs: Triage process#14014

Merged
nzakas merged 3 commits intomasterfrom
triage-process
Feb 11, 2021
Merged

Docs: Triage process#14014
nzakas merged 3 commits intomasterfrom
triage-process

Conversation

@nzakas
Copy link
Copy Markdown
Member

@nzakas nzakas commented Jan 18, 2021

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Wrote up a draft of a new triage process for issues. This new process uses a project board and eliminates a lot of the labels we use for tracking progress. The primary goal is to separate issue management into a triage phase (done by a triage team) and then an evaluating phase (done by the dev team).

Is there anything you'd like reviewers to focus on?

Does the process make sense? Is there anything missing or unclear?

This is intended to be a draft to spur discussion rather than a full-fledged solution.

(Note: This is focused strictly on issues and does not take into account triaging of PRs. If this works for issues we can discuss the best way involve PRs in the process.)

Loading
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion documentation Relates to ESLint's documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants