This plan captures our work in June. We will ship in early July. This is a 4-week iteration.

Endgame

• June 29th, 2020: Endgame begins
• July 3rd, 2020: Endgame done

The endgame details for this iteration are tracked in #101289.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Accessibility

• Accessibility issues, see query @isidorn
• Community call #99916 @sana-ajani @isidorn

Workbench

• Review settings-sync end-to-end flow #100426 @misolori @sandy081
• 🏃 Use encrypted keychain for account management #95475 @RMacfarlane @sbatten
• Enable rich hovers across the workbench (custom trees, terminal) #97496 @Tyriar
• Improve first run experience (open editors, npm scripts, ...) #98614 @misolori @isidorn
• Provide object editing support in the settings editor #99635 @9at8
• Improve Editor Inputs to better support moving and splitting of editors #99770 @jrieken @rebornix @bpasero
• 🏃 Undo/redo of workspace edit file operations, #91383 @jrieken
• Support multiple files in working copy file service #98309 @bpasero
• Git: Restore diff editors on reload #99290 @bpasero

Notebook Editor

• Support for Python adoption https://github.com/microsoft/vscode-python/issues/10496#issuecomment-626028704 @rebornix
• Stabilization query @roblourens @rebornix
• Polish notebook behavior query @roblourens @rebornix
• Improve notebook UX using indentation, borders, colors query @misolori
• Provide a yeoman generator for the notebook renderer starter #101056 @connor4312
• Develop and end-to-end sample that maps many cells to a single LS document, #100186 @jrieken
• Provide a notebook SDK (documentation, samples) microsoft/vscode-docs#3784 @JacksonKearl
• Explore a PowerBI custom output renderer #100759 @sbatten
• Allow to edit markdown documents as notebooks for better self-hosting coverage #100307 @roblourens
• Investigate how to make persisted cell breakpoints robust #99943 @weinand
• Finish the notebook debug sample extension including support for simplified cell debugging #99945 #99946 @weinand

Languages

LSP / LSIF

• Finish support for semantic coloring in the LSP spec @dbaeumer
• Support to defer the calculation of additionalTextEdits until the completion item is resolved microsoft/language-server-protocol#1003 @dbaeumer

TypeScript/JavaScript

• Use TS v4.0 for our building VS Code #100796 @mjbvz

Debug

• Improve the single file debug experience #92269 @weinand @isidorn
• Explore how to make the debug terminal easier to discover #98054 @connor4312
• Investigate support of webview debugging #96626 @connor4312 @weinand
• Unclutter the Call Stack view by eliminating parent debug session #99736 @isidorn @connor4312 @weinand

SCM

• Unify SCM views to support the flexible workbench layout #90461 @joaomoreno

API

• API finalization: query
• API proposals: query

Web

• Improve the support for large file uploads #83565 @bpasero

Extensions

• Review client/marketplace interactions #98366 @sandy081
• Update to the latest extension category names #100399 @sandy081 @fiveisprime
• Support badges from GitHub actions microsoft/vscode-vsce#389 depends on microsoft/vsmarketplace#19 @joaomoreno

Extension Contributions

• Improvements to the Remote extensions microsoft/vscode-remote-release#3175 team
• Improvements to the GitHub PR and Issues extension, see query @alexr00
• Improvements to the Hex editor extension microsoft/vscode-hexeditor#48 @lramos15
• Investigate SDK deprecations for the Azure Account extensions microsoft/vscode-azure-account#140 @RMacfarlane

Install

• 🏃 Explore msix installer for VS Code on Windows #61793 @sbatten
• Explore winget support (update manifest on release, support insiders version) #100745 @lszomoru @fiveisprime

Engineering

• Provide ripgrep binaries for Windows on ARM #98587 @roblourens

Bots

• Improve issue bot models by training them on GPUs #100202 @JacksonKearl
• Publish code of the issue triaging extension https://github.com/microsoft/vscode-github-triage-extension @JacksonKearl
• ✋ Make issue triaging extension available in browser store(s) microsoft/vscode-github-triage-extension#2 @JacksonKearl

Electron

• Investigate start-up performance issues when using electron 8 #97638 @deepak1556 @jrieken
• 🏃 Upgrade to electron 8 #100731 @deepak1556

Node.js-free, sandboxed renderer ⬛

Backlog: #92164

• Debt: adopt service based IPC communication over raw IPC @bpasero
• OOPIF support with custom protocols for desktop #95955 @mjbvz @deepak1556 @alexdima
• 🏃 Remove dependency on node for startup path #98682 ⬛ @deepak1556 @bpasero
  • adopt V8 cached data option for browser windows @deepak1556
  • move off file:// protocol for serving static assets @deepak1556
• 🏃 Support for encodings in sandboxed/web environments (iconv-lite) #79275 @bpasero
• Minimal sandboxed version of the workbench with stubbed services ⬛ @bpasero @deepak1556
• ⬛ enable sandbox: true and contextIsolation for some of our windows to get our feet wet @deepak1556
  • proxy auth dialog
  • issue reporter
  • process explorer

Documentation

• None.

Deferred Items

• Improve existing Windows installer #61793 @lszomoru @joaomoreno
• 🔴 Offer to create fork on GitHub when user has no commit rights to a repository @joaomoreno
• Simplify the Git '...' menu and introduce submenus, depends on #100172 @joaomoreno
• First run experience: simplify Extensions view overflow menu #100756 @sandy081
• Investigate into contentEditable for the hidden accessibility 'textArea' #97154 @isidorn
• Adding a table widget (used for example in a variable/data view in the debugger) #99997 @isidorn
• Investigate issues introduced by the Web UI stopped indication #100757 @weinand @isidorn
• 💪 Explore tabular variables debug view (depends on adding a table widget see above) #100205 @weinand @isidorn
• 💪 Support Jupyter-like cell folding #100308 @roblourens
• 💪 Support Linux ARM64 #6442 @joaomoreno
• 💪 Provide guidelines for extension authors how to adopt the GH auth provider #100995 @RMacfarlane