You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/MAINTAINING.md
+20
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,9 @@
5
5
-[Maintaining](#maintaining)
6
6
-[Workflow](#workflow)
7
7
-[Milestones](#milestones)
8
+
-[Triage](#triage)
8
9
-[Project Boards](#project-boards)
10
+
-[Versioning](#versioning)
9
11
10
12
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
11
13
@@ -36,10 +38,28 @@ Here are the milestones we use and how we use them:
36
38
37
39
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.
38
40
41
+
### Triage
42
+
43
+
We use the following process for triaging GitHub issues:
44
+
45
+
1. a submitter creates an issue
46
+
1. add appropriate labels
47
+
1. if we need to look into it further, add "needs-investigation"
48
+
1. add to milestone
49
+
1. if it should be fixed soon, add to version milestone or "On Deck"
50
+
1. if not urgent, add to "Backlog"
51
+
1. otherwise, add to "Backlog Candidate" if it should be considered
52
+
39
53
### Project Boards
40
54
41
55
We use project boards for projects or goals that span multiple milestones.
42
56
43
57
Think of this as a place to put miscellaneous things (like testing, clean up stuff, etc). As a maintainer, random todos may come up here and there. This gives you a place to add notes temporarily before opening a new issue. Given that our release milestones function off of issues, we believe tasks should have dedicated issues.
44
58
45
59
It also gives us a way to separate the issue triage from bigger-picture, long-term work.
60
+
61
+
## Versioning
62
+
63
+
`<major.minor.patch>`
64
+
65
+
The code-server project follows traditional [semantic versioning](ttps://semver.org/), with the objective of minimizing major changes that break backward compatibility. We increment the patch level for all releases, except when the upstream Visual Studio Code project increments its minor version or we change the plugin API in a backward-compatible manner. In those cases, we increment the minor version rather than the patch level.
0 commit comments