This repository was archived by the owner on Feb 1, 2024. It is now read-only.
This repository was archived by the owner on Feb 1, 2024. It is now read-only.
Open
Description
This issue captures community discussion on how we triage issues. This could focus simply on categorizing, making it easy for individuals to find what they might next do, or it could include more prioritization for team-directed selection of issues. GitHub labels could usefully assist triage but require answering: (a) How eagerly to create labels? (b) Who can label issues? Examples of possibly useful types of label include,
- GitHub defaults:
bug,enhancement,question, ... - generic from elsewhere:
performance,security,testing, ... - by component:
validator,tp,sdk,pbft,rest,cli, ... - by language/technology:
js,python,rust, ... - stage of process:
build,install,run, ... - priorities.
Metadata
Metadata
Assignees
Labels
No labels