New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Terminal Status Updates #3600
Labels
Area-User Interface
Issues pertaining to the user interface of the Console or Terminal
Issue-Docs
It's a documentation issue that really should be on MicrosoftDocs/Console-Docs
Needs-Tag-Fix
Doesn't match tag requirements
Product-Terminal
The new Windows Terminal.
Milestone
Comments
cinnamon-msft
added
Product-Conhost
For issues in the Console codebase
Product-Cmd.exe
The issue is related to the legacy command interpreter, CMD.exe.
Area-Interop
Communication between processes
Issue-Docs
It's a documentation issue that really should be on MicrosoftDocs/Console-Docs
Area-Rendering
Text rendering, emoji, complex glyph & font-fallback issues
Area-Performance
Performance-related issue
Product-Conpty
For console issues specifically related to conpty
Area-Input
Related to input processing (key presses, mouse, etc.)
Area-Output
Related to output processing (inserting text into buffer, retrieving buffer text, etc.)
Area-Interaction
Interacting with the vintage console window (as opposed to driving via API or hooks)
Area-Server
Down in the muck of API call servicing, interprocess communication, eventing, etc.
Area-VT
Virtual Terminal sequence support
Area-Fonts
Related to the font
Area-User Interface
Issues pertaining to the user interface of the Console or Terminal
Area-TerminalConnection
Issues pertaining to the terminal<->backend connection interface
Area-Build
Issues pertaining to the build system, CI, infrastructure, meta
Area-TerminalControl
Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
Area-Extensibility
A feature that would ideally be fulfilled by us having an extension model.
Area-Accessibility
Issues related to accessibility
Area-Settings
Issues related to settings and customizability, for console or terminal
Product-Terminal
The new Windows Terminal.
Product-Meta
The product is the management of the products.
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
Area-AzureShell
Workitems pertaining to the Azure Cloud Shell connection.
Area-Quality
Stability, Performance, Etc.
Area-Schema
Things that have to do with the json schema.
Area-WPFControl
Things related to the WPF version of the TermControl
labels
Nov 15, 2019
ghost
added
the
Needs-Triage
It's a new issue that the core contributor team needs to triage at the next triage meeting
label
Nov 15, 2019
October 25, 2019 StatusClick to expand to see the status update!Recent News / ReleasesTerminal 1910 was released on Wednesday
Current StatusPlan for 1911 is in place
Cascadia Code
Ignite Session
Windows In-box Console/ConHost 20H1 IssuesTerminal 1911 WorkTerminal Roadmap |
DHowett-MSFT
removed
the
Area-Server
Down in the muck of API call servicing, interprocess communication, eventing, etc.
label
Nov 16, 2019
December 5, 2019 StatusClick to expand to see the status update!Recent News / ReleasesTerminal v0.7 was released on Tuesday 11/26
Terminal v0.8 is scheduled for 1/7
Cascadia Code
Community NewsNode+JS Interactive
Terminal 1912 WorkTerminal Roadmap |
January 9, 2020 StatusClick to expand to see the status update!Recent News / ReleasesTerminal v0.8 will be released on Tuesday 1/14
Terminal v0.8 WorkTerminal v0.9 WorkTerminal Roadmap |
DHowett-MSFT
removed
Area-Accessibility
Issues related to accessibility
Area-AzureShell
Workitems pertaining to the Azure Cloud Shell connection.
Area-Build
Issues pertaining to the build system, CI, infrastructure, meta
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
Area-Extensibility
A feature that would ideally be fulfilled by us having an extension model.
Area-Fonts
Related to the font
Area-Input
Related to input processing (key presses, mouse, etc.)
Area-Interaction
Interacting with the vintage console window (as opposed to driving via API or hooks)
Area-Output
Related to output processing (inserting text into buffer, retrieving buffer text, etc.)
Area-Performance
Performance-related issue
Area-Quality
Stability, Performance, Etc.
Area-Rendering
Text rendering, emoji, complex glyph & font-fallback issues
Area-Schema
Things that have to do with the json schema.
Area-Settings
Issues related to settings and customizability, for console or terminal
Area-TerminalConnection
Issues pertaining to the terminal<->backend connection interface
Area-TerminalControl
Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
Area-VT
Virtual Terminal sequence support
Area-WPFControl
Things related to the WPF version of the TermControl
labels
Jan 22, 2020
January 31, 2020 StatusClick to expand to see the status update!Recent News / ReleasesTerminal v0.9 is scheduled for 2/11
Community NewsOne Dev Minute Videos
Terminal v0.9 WorkTerminal Roadmap |
April 3, 2020 StatusRecent News / ReleasesSettings changes are coming
Terminal v1.0 WorkTerminal Roadmap |
We've kinda gone in another direction with posting status updates. I'm gonna close this one out for now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Area-User Interface
Issues pertaining to the user interface of the Console or Terminal
Issue-Docs
It's a documentation issue that really should be on MicrosoftDocs/Console-Docs
Needs-Tag-Fix
Doesn't match tag requirements
Product-Terminal
The new Windows Terminal.
This issue contains all of the status updates for Windows Terminal. This helps provide insight into where the project is at between releases.
Feel free to subscribe to this issue to receive updates whenever we post another status update.
Comments have been disabled for this issue in order to reduce noise. Please use this issue for any discussion relating to status updates.
The text was updated successfully, but these errors were encountered: