Repository: microsoft/terminal (language: cpp)

Issue:
Updates to Terminal repo milestones, 2022 edition
The Terminal repo right now consists of a collection of various different "milestones" that have evolved organically over the years. We've got Console milestones, we've got Terminal milestones, we have milestones that vaguely align with OS releases, and then we've got like, four different milestones that are all the "backlog" in one way or another ("Console Backlog", "Terminal Backlog", "Windows vNext", and "Icebox"). All together, they don't create a very clear picture of what's going on in the Terminal land. To try and clear this up, we're going to de-duplicate some of these, and try something new for 2022. 

* The "Console Backlog" and the "Terminal Backlog" are both getting deprecated. They'll be collectively replaced with just a unified **"Backlog"** milestone, which will track things we'd like to get to, but we don't have any time planned for. 
* "Windows vNext" is also being deprecated. Originally, it was a rolling milestone to track things that should be in "the next version of Windows". Unfortunately, it wasn't tracked super well, so it's effectively become a second Console Backlog.
* We're going to use four milestones for tracking bits of the next _year_ of planning. These are separated into two "release" milestones, and two "semester" milestones.
  - **"Terminal v1.{n}"** (as of when this was written, this is v1.13): Shots we're calling for the upcoming release. Features & tasks we expect to land, blocking bugfixes, or other high-pri fixes
  - **"Terminal v1.{n+1}"** (currently, v1.14): Same as above, for the following release. With two 6-week release milestones, this is about 3 months of planning. This is a useful buffer for "we really should do this SOON, but not ASAP. 
  - **"22H1"** will represent the first 6 months of 2022. This will help align internally with the OS release cadence. 
    - If there are `conhost` bugs that need to get fixed in the upcoming release of Windows, then they go here. 
    - Accessibility bugs will also go here, or into the current semester. 
  - **"22H2"** is the same idea. A planning buffer for the second half of 2022. This includes Terminal features we expect to land in the second half. 
    - Terminal P2+ bugs will go here. 
* Terminal v2, Console Backlog, Terminal Backlog, Windows vNext are all going to be emptied into "22H1", "22H2", and the "Backlog", based on current priority labels. 
* We're also going to rename "Terminal v3" to **Up Next"**. This is for features, we think are highest on the backlog. The next big set of features we want to work on. Things that should be at the top of our list to fill up the upcoming semester.
* We're leaving the **""Icebox"** as-is right now, albeit, possibly workshopping the name in the near future. This will remain for features that we think are cool, valid feature requests for the Console&Terminal. However, we'll admit we're never going get to these features. <!-- Space is expanding so fast between us and these issues, that even travelling at the speed of light we'd never get to them.  --> <!-- These issues have escaped our team's gravity well. --> We'd likely accept PRs from the community for things in here. 
* We had a really successful **"Engineering Improvements"** milestone over the last few weeks, so we'll probably try that again next year. At the end of each year, I'll just move the closed issues in the EIM milestone to a specific "Engineering Improvements {current_year}" milestone. 

We're intentionally not planning out more specifically that 1.n and 1.n+1 - we're generally a fairly responsive team, where priorities can shift quickly during the course of the year. Trying to lick cookies for specific milestones more than 3 months out has generally been an exercise in futility. 

As always, as priorities shift, and resourcing changes, issues can move between these milestones fluidly. 

Hopefully, by grouping bugs into semester-sized milestones, we can address some of them in a timelier fashion. Currently, they just get stuck into "Terminal v2", which we've been pulling features and tasks into as well, which has only created a longer bug backlog 😄.

I'll be going through and moving our issues into this new structure likely sometime early in 2022. 

If this doesn't end up working, we'll take our learnings and try something else for 2023 😄 


Discussion / hints:

Fix patch:
diff --git a/doc/roadmap-2022.md b/doc/roadmap-2022.md
new file mode 100644
index 00000000000..a85f88f8cf0
--- /dev/null
+++ b/doc/roadmap-2022.md
@@ -0,0 +1,72 @@
+# Terminal 2022 Roadmap
+
+## Overview 
+
+This document outlines the roadmap of features we're planning for the Windows Terminal during 2022. This serves as a successor to the [Terminal v2 Roadmap], to reflect changes to our planning going forward.
+
+Initially we had planned on a discrete "Terminal v2" goal, but over the last 18 months it's become clear to the team that we don't need a strict "2.0" release. We can continue serving the community effectively with continual, incremental updates. Should a future release warrant a substantial change to the Terminal worthy of the "2.0" moniker, we can re-evaluate then.
+
+In 2022, we're going to try tracking our overall work with two "semester" milestones, "[22H1]" and "[22H2]", which roughly align with internal deadlines. Although the Windows Terminal ships updates out-of-band from the rest of the OS, we still have commitments to fixing bugs in the broader console ecosystem. Those changes need to be made in sync with the rest of the OS. Aligning our external milestones with those deadlines should help make sure we get bugs resolved in a timely fashion and checked into the OS.
+
+These have additionally inherited the remainder of the work that was originally targeting the Terminal v2 milestone. As we burn down the features and bugs in these milestones, we'll draw new features into them from the "[Up Next]" milestone, which is itself populated from the highest-priority elements of the [Backlog].
+
+## Milestones
+
+Windows Terminal is engineered and delivered as a set of 6-week milestones. New features will go into [Windows Terminal Preview](https://aka.ms/terminal-preview) first, then a month after they've been in Preview, those features will move into [Windows Terminal](https://aka.ms/terminal). These timelines are rough estimates, not strict rules.
+
+## Terminal Roadmap / Timeline
+
+Below is the schedule for when milestones will be included in release builds of Windows Terminal and Windows Terminal Preview. The dates are rough estimates and are subject to change.
+
+
+| Milestone End Date | Milestone Name | Preview Release Blog Post |
+| ------------------ | -------------- | ------------------------- |
+| 2020-06-18 | [1.1] in Windows Terminal Preview | [Windows Terminal Preview 1.1 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-1-release/) |
+| 2020-07-31 | [1.2] in Windows Terminal Preview<br>[1.1] in Windows Terminal | [Windows Terminal Preview 1.2 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-2-release/) |
+| 2020-08-31 | [1.3] in Windows Terminal Preview<br>[1.2] in Windows Terminal | [Windows Terminal Preview 1.3 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-3-release/) |
+| 2020-09-30 | [1.4] in Windows Terminal Preview<br>[1.3] in Windows Terminal | [Windows Terminal Preview 1.4 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-4-release/) |
+| 2020-11-30 | [1.5] in Windows Terminal Preview<br>[1.4] in Windows Terminal | [Windows Terminal Preview 1.5 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-5-release/) |
+| 2021-01-31 | [1.6] in Windows Terminal Preview<br>[1.5] in Windows Terminal | [Windows Terminal Preview 1.6 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-6-release/) |
+| 2021-03-01 | [1.7] in Windows Terminal Preview<br>[1.6] in Windows Terminal | [Windows Terminal Preview 1.7 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-7-release/) |
+| 2021-04-14 | [1.8] in Windows Terminal Preview<br>[1.7] in Windows Terminal | [Windows Terminal Preview 1.8 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-8-release/) |
+| 2021-05-31 | [1.9] in Windows Terminal Preview<br>[1.8] in Windows Terminal | [Windows Terminal Preview 1.9 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-9-release/) |
+| 2021-07-14 | [1.10] in Windows Terminal Preview<br>[1.9] in Windows Terminal | [Windows Terminal Preview 1.10 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-10-release/) |
+| 2021-08-31 | [1.11] in Windows Terminal Preview<br>[1.10] in Windows Terminal | [Windows Terminal Preview 1.11 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-11-release/) |
+| 2021-10-20 | [1.12] in Windows Terminal Preview<br>[1.11] in Windows Terminal | [Windows Terminal Preview 1.12 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-12-release/) |
+|  | [1.13] in Windows Terminal Preview<br>[1.12] in Windows Terminal |  |
+|  | [1.14] in Windows Terminal Preview<br>[1.13] in Windows Terminal |  |
+
+
+## Issue Triage & Prioritization
+
+Incoming issues/asks/etc. are triaged several times a week, labeled appropriately, and assigned to a milestone in priority order:
+
+* P0 (serious crashes, data loss, etc.) issues are scheduled to be dealt with ASAP. These go in the current release milestone (e.g. at time of writing, these would go into 1.13).
+* P1 issues/features/asks are typically assigned to the current or the following release milestone.
+* P2 & P3 issues will typically go in the second semester for the year.
+* Accessibility and Console issues that need to go into the Windows OS typically go into the current semester.
+* Issues/features/asks not related to existing features in the 22H1/22H2 semesters are assigned to the [Backlog] for subsequent triage, prioritization & scheduling.
+
+
+[1.1]: https://github.com/microsoft/terminal/milestone/24
+[1.2]: https://github.com/microsoft/terminal/milestone/25
+[1.3]: https://github.com/microsoft/terminal/milestone/26
+[1.4]: https://github.com/microsoft/terminal/milestone/28
+[1.5]: https://github.com/microsoft/terminal/milestone/30
+[1.6]: https://github.com/microsoft/terminal/milestone/31
+[1.7]: https://github.com/microsoft/terminal/milestone/32
+[1.8]: https://github.com/microsoft/terminal/milestone/33
+[1.9]: https://github.com/microsoft/terminal/milestone/34
+[1.10]: https://github.com/microsoft/terminal/milestone/35
+[1.11]: https://github.com/microsoft/terminal/milestone/36
+[1.12]: https://github.com/microsoft/terminal/milestone/38
+[1.13]: https://github.com/microsoft/terminal/milestone/39
+[1.14]: https://github.com/microsoft/terminal/milestone/41
+
+
+[22H1]: https://github.com/microsoft/terminal/milestone/43
+[22H2]: https://github.com/microsoft/terminal/milestone/44
+[Up Next]: https://github.com/microsoft/terminal/milestone/37
+[Backlog]: https://github.com/microsoft/terminal/milestone/45
+
+[Terminal v2 Roadmap]: https://github.com/microsoft/terminal/tree/main/doc/terminal-v2-roadmap.md
diff --git a/doc/terminal-v2-roadmap.md b/doc/terminal-v2-roadmap.md
index 9db0aa65298..a7484bbe7d6 100644
--- a/doc/terminal-v2-roadmap.md
+++ b/doc/terminal-v2-roadmap.md
@@ -1,5 +1,9 @@
 # Terminal 2.0 Roadmap
 
+> **NOTE**
+>
+> This document has been superseded by the [Terminal 2022 Roadmap]. Please refer to that document for the updated roadmap.
+
 ## Overview
 
 This document outlines the roadmap towards delivering Windows Terminal 2.0.
@@ -32,8 +36,6 @@ Below is the schedule for when milestones will be included in release builds of
 | 2021-07-14 | [1.10] in Windows Terminal Preview<br>[1.9] in Windows Terminal | [Windows Terminal Preview 1.10 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-10-release/) |
 | 2021-08-31 | [1.11] in Windows Terminal Preview<br>[1.10] in Windows Terminal | [Windows Terminal Preview 1.11 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-11-release/) |
 | 2021-10-20 | [1.12] in Windows Terminal Preview<br>[1.11] in Windows Terminal | [Windows Terminal Preview 1.12 Release](https://devblogs.microsoft.com/commandline/windows-terminal-preview-1-12-release/) |
-|  | 2.0 RC in Windows Terminal Preview<br>2.0 RC in Windows Terminal | |
-|  | [2.0] in Windows Terminal Preview<br>[2.0] in Windows Terminal | |
 
 ## Issue Triage & Prioritization
 
@@ -139,3 +141,5 @@ Feature Notes:
 [#632]: https://github.com/microsoft/terminal/issues/632
 [#4472]: https://github.com/microsoft/terminal/issues/4472
 [#8048]: https://github.com/microsoft/terminal/pull/8048
+
+[Terminal 2022 Roadmap]: https://github.com/microsoft/terminal/tree/main/doc/roadmap-2022.md


Test patch: