docs(maintaining): use milestones over boards

[jsjoeio]

Current Workflow

Right now, the workflow looks a bit like this:

1. Issue comes in, assign to "triage" and ad relevant labels.
2. Once triaged is moved to next, it means we are working on it.
3. It may also get added to a version milestone if it will be out before that milestone is released.

We also have some work being added to the "On Deck" milestone. We would like to reduce any duplicate efforts and align ourselves with one process.

Proposed Workflow

Use milestones instead of project boards (similar to how vscode does it).

Create the following milestones:

• "Backlog" -> Work not yet planned for a specific release.
• "On Deck" -> Work under consideration for upcoming milestones
• "Backlog Candidates" -> Work that is not yet accepted for the Backlog. We wait for the community to weigh in

Month milestones make more sense than version milestones because in the event that a milestone has work that affects the version then we'd need to change the milestone name.

Pros

• Milestones live closer to the issues
• Milestones have progress indicators (open vs. closed in milestones)
• Milestones can have due dates
• Milestones can have descriptions

Cons

• Issues can be attached to multiple milestones. This could lead to problems (potentially).

Proposed Changes

Once we this PR is approved, these are the changes I (@jsjoeio) will own and take care of as part of this process:

• Create "Backlog" milestone
• Create "Backlog Candidates" milestone
• Move all issues under "triage" in code-server project board to "Backlog" milestone
• Move all issues under "Next" in code-server project board to "On Deck" milestone (if not already in version milestone)

Follow-up

• PR with proposal for changes to our triage workflow
• PR with proposal for documenting our versioning (aka how we bump versions)
• refactor/clean up our project boards (hopefully removing all except 🗺️ Roadmap)

[codecov]

Codecov Report

Merging #3228 (9639ed6) into main (9f7ceef) will not change coverage.
The diff coverage is n/a.

❗ Current head 9639ed6 differs from pull request most recent head d07317a. Consider uploading reports for the commit d07317a to get more accurate results

@@           Coverage Diff           @@
##             main    #3228   +/-   ##
=======================================
  Coverage   46.90%   46.90%           
=======================================
  Files          23       23           
  Lines        1196     1196           
  Branches      237      237           
=======================================
  Hits          561      561           
  Misses        451      451           
  Partials      184      184           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f7ceef...d07317a. Read the comment docs.

[bpmct]

this looks great!

[jsjoeio]

UPDATE: discussed a bit with @code-asher offline. We're leaning in favor of version milestones (instead of monthly milestones) because of this scenario:

• issue is attached to April 2021.
• we decide to cut an early release halfway through (includes fix for issue)
• issue gets closed, but when I look at milestone, still open because month isn't over (aka milestone not closed)

Now you have to check commits and see if it's in the version or not (more work for maintainers + community).

[code-asher]

Overall looks great!