a
/
code-server
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs(maintaining): add triage to workflow

This commit is contained in:
Joe Previte 2021-05-04 11:57:00 -07:00
parent 1070db7e27
commit 1c9156c504
No known key found for this signature in database
GPG Key ID: 2C91590C6B742C24
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/MAINTAINING.md
View File

@ -5,6 +5,7 @@
- [Maintaining](#maintaining)
- [Workflow](#workflow)
- [Milestones](#milestones)
- [Triage](#triage)
- [Project Boards](#project-boards)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
@ -36,6 +37,18 @@ Here are the milestones we use and how we use them:
With this flow, any un-assigned issues are essentially in triage state and once triaged are either "Backlog" or "Backlog Candidates". They will eventually move to "On Deck" (or be closed). Lastly, they will end up on a version milestone where they will be worked on.
### Triage
We use the following process for triaging GitHub issues:
1. a submitter creates an issue
1. add appropriate labels
1. if we need to look into it further, add "needs-investigation"
1. add to milestone
1. if it should be fixed soon, add to version milestone or "On Deck"
1. if not urgent, add to "Backlog"
1. otherwise, add to "Backlog Candidate" if it should be considered
### Project Boards
We use project boards for projects or goals that span multiple milestones.