Iteration Plan for June 2020

[kieferrm]

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:

Mark	Description
🏃	work in progress
✋	blocked task
💪	stretch goal for this iteration
🔴	missing issue reference
🔵	more investigation required to remove uncertainty
⚫	under discussion within the team
⬛	a large work item, larger than one iteration

Accessibility

• Accessibility issues, see query @isidorn
• Community call VS Code Accessibility Call - June 2020 #99916 @sana-ajani @isidorn

Workbench

• Review settings-sync end-to-end flow Polish settings-sync UI #100426 @misolori @sandy081
• 🏃 Use encrypted keychain for account management Use encrypted keychain for account management #95475 @RMacfarlane @sbatten
• Enable rich hovers across the workbench (custom trees, terminal) Move generic hover widget to base ui and extend in ContentHoverWidget #97496 @Tyriar
• Improve first run experience (open editors, npm scripts, ...) Improve first run experience #98614 @misolori @isidorn
• Provide object editing support in the settings editor Edit object type settings from the settings GUI #99635 @9at8
• Improve Editor Inputs to better support moving and splitting of editors Revisit lifecycle of editor inputs in VSCode #99770 @jrieken @rebornix @bpasero
• 🏃 Undo/redo of workspace edit file operations, Support file operations (create, rename, delete) in cross file undo #91383 @jrieken
• Support multiple files in working copy file service Support multiple files in working copy file service #98309 @bpasero
• Git: Restore diff editors on reload 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 Add notebook renderer starter to yeoman generators #101056 @connor4312
• Develop and end-to-end sample that maps many cells to a single LS document, Language service use of a whole notebook as single (concat) document #100186 @jrieken
• Provide a notebook SDK (documentation, samples) Provide a notebook SDK vscode-docs#3784 @JacksonKearl
• Explore a PowerBI custom output renderer Embedded Power BI Notebook Renderer Exploration #100759 @sbatten
• Allow to edit markdown documents as notebooks for better self-hosting coverage Support editing markdown files as notebooks #100307 @roblourens
• Investigate how to make persisted cell breakpoints robust Investigate how to make persisted cell breakpoints robust #99943 @weinand
• Finish the notebook debug sample extension including support for simplified cell debugging document how to use existing debug extensions for notebooks #99945 Document how to integrate xeus for notebook debugging #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 new client capability: defer calculation additionalTextEdit until comletionItem/resolve language-server-protocol#1003 @dbaeumer

TypeScript/JavaScript

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

Debug

• Improve the single file debug experience Explore improving the single file debug experience #92269 @weinand @isidorn
• Explore how to make the debug terminal easier to discover js-debug debugger terminal discoverability  #98054 @connor4312
• Investigate support of webview debugging Debugging webviews in VS Code #96626 @connor4312 @weinand
• Unclutter the Call Stack view by eliminating parent debug session Unclutter CALL STACK view by eliminating parent debug session  #99736 @isidorn @connor4312 @weinand

SCM

• Unify SCM views to support the flexible workbench layout Enable SCM Views to move to panel #90461 @joaomoreno

API

• API finalization: query
• API proposals: query

Web

• Improve the support for large file uploads Web: improve the experience for large file uploads #83565 @bpasero

Extensions

• Review client/marketplace interactions endless loop while updating extension #98366 @sandy081
• Update to the latest extension category names Add support for new extension categories #100399 @sandy081 @fiveisprime
• Support badges from GitHub actions Add github.com as badge provider vscode-vsce#389 depends on Only one extension appears when trying to find "aspnet" extensions vsmarketplace#19 @joaomoreno

Extension Contributions

• Improvements to the Remote extensions Remote: Iteration Plan for June 2020 vscode-remote-release#3175 team
• Improvements to the GitHub PR and Issues extension, see query @alexr00
• Improvements to the Hex editor extension Iteration Plan June 2020 vscode-hexeditor#48 @lramos15
• Investigate SDK deprecations for the Azure Account extensions Compatibility with new Azure SDK vscode-azure-account#140 @RMacfarlane

Install

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

Engineering

• Provide ripgrep binaries for Windows on ARM Complete win32-arm64 implementation #98587 @roblourens

Bots

• Improve issue bot models by training them on GPUs Adopt GPU-based issue classification #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) Release in chrome extension store vscode-github-triage-extension#2 @JacksonKearl

Electron

• Investigate start-up performance issues when using electron 8 Investigating Electron 8 exploration startup performance  #97638 @deepak1556 @jrieken
• 🏃 Upgrade to electron 8 Update to Electron 9 #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 'webview.getWebContents()' is deprecated and will be removed #95955 @mjbvz @deepak1556 @alexdima
• 🏃 Remove dependency on node for startup path Remove dependency on node require for startup code 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) Web: support other encodings than UTF-8 #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 MSIX 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 Add API support for submenus #100172 @joaomoreno
• First run experience: simplify Extensions view overflow menu Review and clean up overflow actions in extensions viewlet #100756 @sandy081
• Investigate into contentEditable for the hidden accessibility 'textArea' Use contentEditable for our hidden accessibility textArea #97154 @isidorn
• Adding a table widget (used for example in a variable/data view in the debugger) Support table widget #99997 @isidorn
• Investigate issues introduced by the Web UI stopped indication Improving stopped indication ("breakpoint hit") for Web UI #100757 @weinand @isidorn
• 💪 Explore tabular variables debug view (depends on adding a table widget see above) Add a tabular variables view for debugging #100205 @weinand @isidorn
• 💪 Support Jupyter-like cell folding Implement Jupyter-style cell folding #100308 @roblourens
• 💪 Support Linux ARM64 Official Support for ARM/Raspberry Pi Linux (armhf, arm64) #6442 @joaomoreno
• 💪 Provide guidelines for extension authors how to adopt the GH auth provider Documentation for consuming authentication providers #100995 @RMacfarlane

[gjsjohnmurray]

Based on #93598 (comment) it looks like there's a better issue to link object editing support to, namely #99635

[yubaoquan]

Why not skip electron 8, use 9 instead?
I remember there is a history vscode skipped a major version of electron.

[deepak1556]

@yubaoquan we found out quite a few blocking issues when we started exploring Electron 8 https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Aelectron-8-update, jumping versions would only make it difficult to narrow down the issue and get them fixed in a timely manner. When we push Electron 8 to insiders, Electron 9 will adopted into our exploration builds, upgrading to Electron 9 was also blocked by #95955 which got fixed yesterday.

To top it all I would say, its too soon to skip versions :)