8
8
- [ Workflow] ( #workflow )
9
9
- [ Milestones] ( #milestones )
10
10
- [ Triage] ( #triage )
11
- - [ Project boards] ( #project-boards )
12
11
- [ Versioning] ( #versioning )
13
12
- [ Pull requests] ( #pull-requests )
14
13
- [ Merge strategies] ( #merge-strategies )
@@ -42,7 +41,7 @@ Occasionally, other Coder employees may step in time to time to assist with code
42
41
43
42
To onboard a new maintainer to the project, please make sure to do the following:
44
43
45
- - [ ] Add to [ coder/code-server-reviewers ] ( https://github.com/orgs/coder/teams/code-server-reviewers )
44
+ - [ ] Add to [ coder/code-server] ( https://github.com/orgs/coder/teams/code-server )
46
45
- [ ] Add as Admin under [ Repository Settings > Access] ( https://github.com/coder/code-server/settings/access )
47
46
- [ ] Add to [ npm Coder org] ( https://www.npmjs.com/org/coder )
48
47
- [ ] Add as [ AUR maintainer] ( https://aur.archlinux.org/packages/code-server/ ) (talk to Colin)
@@ -72,7 +71,7 @@ Here are the milestones we use and how we use them:
72
71
- "On Deck" -> Work under consideration for upcoming milestones.
73
72
- "Backlog Candidates" -> Work that is not yet accepted for the backlog. We wait
74
73
for the community to weigh in.
75
- - "<0.0.0 >" -> Work to be done for a specific version .
74
+ - "<Month >" -> Work to be done for said month .
76
75
77
76
With this flow, any un-assigned issues are essentially in triage state. Once
78
77
triaged, issues are either "Backlog" or "Backlog Candidates". They will
@@ -91,19 +90,6 @@ We use the following process for triaging GitHub issues:
91
90
2 . If not urgent, add to "Backlog"
92
91
3 . Otherwise, add to "Backlog Candidate" for future consideration
93
92
94
- ### Project boards
95
-
96
- We use project boards for projects or goals that span multiple milestones.
97
-
98
- Think of this as a place to put miscellaneous things (like testing, clean up
99
- stuff, etc). As a maintainer, random tasks may come up here and there. The
100
- project boards give you places to add temporary notes before opening a new
101
- issue. Given that our release milestones function off of issues, we believe
102
- tasks should have dedicated issues.
103
-
104
- Project boards also give us a way to separate the issue triage from
105
- bigger-picture, long-term work.
106
-
107
93
## Versioning
108
94
109
95
` <major.minor.patch> `
0 commit comments