Iteration Plan for January 2021

[kieferrm]

This plan captures our work in late December and January. This is a 6-week iteration. We will ship in early February.

Note: Our last Insiders build of 2020 will go out on December 22. The first Insiders build of 2021 will go out on January 5. Our team will have minimal presence between December 19 and January 3. Expect slow or no responses in this time frame. Thank you for your support and contributions in 2020! Happy Holidays to all of you.

Endgame

• January 25, 2021: Endgame begins
• January 29, 2021: Endgame done

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

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 team
• 🏃 Assess notebook accessibility VS Code native notebook accessibility improvement #111255 @isidorn @rebornix @roblourens

Workbench

• 🏃 Explore the concept of Trusted Workspaces General Discussion on Workspace Trust Feature #106488 @lszomoru @sbatten
• Investigate predefined file filters in search Investigate predefined file filters search #106790 @JacksonKearl
• 🏃 Improve the welcome pages Explore improvements to welcome pages #106715 @misolori @JacksonKearl @digitarald
• 🏃 💪 Explore support for adding/organizing imports on Paste Add events for copy/paste to allow language extensions to bring using/import statements along #30066 @mjbvz
• Improve emmet extension perf Tab key is extremely slow on medium-large files when emmet.triggerExpansionOnTab is enabled #71996 @rzhao271
• Migrate emmet dependency to latest Migrate to the latest Emmet #110697 @rzhao271
• Show file decorations in editor tabs Decorations: Show decorations in tabs #49382 @jrieken
• Improve undo/redo from explorer when an extension contributes edits Should send a single FileWillRenameEvent instead of separate events when moving multiple files at once #111867 @jrieken @isidorn
• Allow tabs to wrap to multi-line Allow tabs to wrap to multi-line #70413 @bpasero
• Support to customize the product icons [themes] Add product icon themes #92791 @aeschli
• Provide hovers in comments views Comments View doesn't show a hover with the full text  #108396 @RMacfarlane
• Revisit how activity bar items and status bar items can be hidden by the user Revisit how activity bar items and status bar items can be hidden by the user #113757 @bpasero @sbatten
• 🏃 Explore consolidation of managing "Don't Show Again" in notifications Allow to reset “Don't Show Again” preference #24815 @meganrogge
• Utilize the GH login for the Issue Reporter result of powershell command : help can not be loaded to console #9516 @RMacfarlane
• Introduce a setting to switch between the Search editor and the Search view Open Search Editor by Default #112588 @JacksonKearl

Code Editor

• Inline Hint API and UI proposal, Support inline hints #113276 @jrieken

Notebook Editor

• Identify and fill API gaps for LiveShare API gaps to support Liveshare in Notebook #102503 @rebornix
• Explore notebook keymap support Explore notebook keymap support #106679 @rebornix @roblourens
• 🏃 Explore extensible markdown rendering for notebooks Explore customizing the markdown renderer for notebooks #106701 @mjbvz
• Improve notebook diff editor scrolling performance Scrolling in a notebook diff editor is sluggish #109680 @rebornix
• Explore output renderer support in notebook diff editors https://github.com/microsoft/vscode/issues?q=is%3Aopen+label%3Anotebook+diff @rebornix
• Explore options to support free-floating output renderer elements Notebooks - HTML elements (widgets) in output overflow & get displayed under the editor #108947 @rebornix
• 🏃 Explore options to allow an output to go into full-screen mode Allow an output to go into full-screen mode #110766 @rebornix @deepak1556
• Provide Outline View support for Notebooks Support outline with notebooks #98173 @jrieken
• Improve focus handling in notebooks Improve focus handling in notebooks #113246 @misolori
• Improve discoverability of cell folding Improve discoverability of cell folding  #113248 @misolori @rebornix
• 🏃 Explore cell multi-select Support multi cell selection in notebook #114156 @rebornix @misolori

Languages

LSP /LSIF

• 🏃 LSP - investigate supporting a pull model for diagnostics (diagnostics are currently delivered using a push model) Add support for explicitly requesting diagnostics language-server-protocol#737 @dbaeumer
• Enable showing completion item detail if available for all completion items Consider showing completion item detail if available for all list items #39441 @dbaeumer
• Implement an LSIF index validator Implement a validation tool to ensure that an LSIF conforms to the spec lsif-node#119 @dbaeumer

JavaScript/TypeScript

• Enable TS 4.2 Enable TS 4.2 features  #115255 @mjbvz

Debug

• Update all node debug documentation/tutorials to use debug-js Update JavaScript debugger user doc for js-debug vscode-docs#4123 @connor4312
• Eliminate "preview" term from debuggers (Node, Chrome, ExtDev) Eliminate the term "Preview" from js-debug #112139 @connor4312
• 🏃 Extension API for "Inline Values" Extension API for Inline Values #105690 @weinand
• Improve the "breakpoint hit" UI for Web UI Improving stopped indication ("breakpoint hit") for Web UI #100757 @weinand @isidorn
• Support to edit the condition expression for function breakpoints Function breakpoints - protocol allows condition but no UI to set condition #3646 @isidorn
• Support to start multiple debug sessions from a single launch config Support to start multiple debug sessions from a single launch config #110226 @isidorn
• 🏃 💪 Ability to drag and drop breakpoints Ability to drag and drop breakpoints #88227 @isidorn

DAP

• 🏃 Continue discussion: Support object IDs Proposal: Support object IDs debug-adapter-protocol#134 @weinand
• 🏃 Investigate: Control escaping/quoting arguments for the runInTerminal request add property for controlling escaping arguments for the runInTerminal request debug-adapter-protocol#146 @weinand
• Explore support for large number of threads Better support for large number of green-thread like things debug-adapter-protocol#169 @weinand @connor4312

Testing

• 🏃 Explore how to improve testing support Testing in VS Code #107467 @connor4312 @sandy081

Terminal

• Restore terminal UI state Terminal: remember layout between restarts #109244 @roblourens @meganrogge
• Provide flow control in the terminal to avoid starvation in the case of continuous output Support flow control for the terminal process #113827 @Tyriar @meganrogge
• Investigate memory leak in Terminal Memory leak in terminal support #111562 @meganrogge @Tyriar
• Improve predictive echo for PowerShell Type Ahead isn't "on" for cursor movement when using PowerShell on non-Windows #113853 When using typeahead right arrow should stop at the end of the prompt  #113857 @TylerLeonhardt
• Support Powershell from the Windows Store Make PowerShell 7+ the default shell if it's available #110828 @TylerLeonhardt

Source Control

• Warn when pushing to a rebased branch Warn before pulling if a branch appears to have been rebased #110881 @eamodio
• 💪 Guide user to push to a remote after creating a commit Explore UI additions to help guide users to push to a remote after committing #110882 @eamodio

API

• API finalization: query
• API proposals: query

Extensions

• Provide design and UX guidelines for extension authors Create design guidelines for extension authors #104006 @misolori

Extension Contributions

• Improvements to the Remote extensions Remote Iteration Plan for January 2021 vscode-remote-release#4184 team
• Improvements to the GitHub PR extension Improvements to the PR flow vscode-pull-request-github#2293 @RMacfarlane @eamodio
• Continue improving and adding functionality to REST Book Planning backlog for REST Book tanhakabir/rest-book#30 @tanhakabir

Install

• Explore installing a WSL extension out of the box on Windows Investigation: Installing a WSL extension out of the box on Windows #106759 @joaomoreno @aeschli
• 🔴 Explore to show macOS ARM downloads side by side with the Intel version @deepak1556 @gregvanl

Engineering

• Continuous build optimizations (run tests in parallel) @lszomoru @joaomoreno @alexdima
• 🏃 🔴 Investigate VS Code build optimization: separate the building of the core from the building of the extensions @joaomoreno
• Publish Linux ARM deb, rpm and snap to repositories Publish Linux ARM deb & rpm repositories #106473 @joaomoreno
• Make VSCode Trusted Types compliant Trusted Types compatibility: Make VSCode TrustedTypes compliant #103699 @jrieken and team
• Stabilize Apple Silicon builds Stablize apple silicon exploration builds #106770 @deepak1556
• MacOS universal build Exploration: Universal binary for apple silicon #113851 @deepak1556
• 🏃 electron 11 stabilization https://github.com/microsoft/vscode/issues?q=is%3Aissue+label%3Aelectron-11-update+is%3Aopen @deepak1556 @rzhao271
• 🏃 Terminal lag on Big Sur Integrated Terminal Lags Intermittently  #105446 @deepak1556
• 💪 Scroll performance on Windows Slow reponse to scroll and typing #107016 @deepak1556
• 🏃 Move away from get*Actions in Views and ViewContainers and use Menu instead Review usage/overrides of get.*Actions on ViewPanes #92038 @sandy081 team
• 🔴 Adopt vscode.open and vscode.diff in SCM, Timeline, GHPRI extension
  • Timeline @eamodio
  • 🏃 GHPRI extension @alexr00
  • Custom Views @alexr00
• 🔴 Investigate using component governance support for third party notices generation @lszomoru

Node.js-free, sandboxed renderer

• 🏃 Backlog Implement a node.js-free, sandboxed, context isolated renderer  #92164 @bpasero @deepak1556

[Igorgro]

When new Native Notebook Editor will be available in stable version?

[axetroy]

Digression

I think this statistic (https://vscode-github-stats.netlify.app/) is great.

This is for the vscode team to better manage and maintain the issue.

But I wonder if there are statistics for users, which will count the features that users most want and the bugs that they most want to fix.

Most anticipated features	Most eager to fix
Allow to hide editor title section entirely (tabs, breadcrumbs)	Slow reponse to scroll and typing
Allow multiple views to show at the same time	VS Code was lost on shutdown with pending update
...	...
...	...
...	...
...	...
...	...
...	...
...	...
...	...
...	...
...	...

in technology, it’s not difficult to count this information. (From the issue, you can calculate the number of likes, creating time, number of participants in the discussion, and even the number of vscode team members participating in the discussion)

Because some issues are 2 years or even 3 years ago, and the attention is a lot.

Hope such statistics can help the vscode team to understand what users want most.

Of course, this is not an iteration plan, but it can provide a reference for the vscode team.

thanks for your great work.

[GitMensch]

Because some issues are 2 years or even 3 years ago, and the attention is a lot.

You mean things like #2809... the question is: do the vscode team want these statistics?

[GitMensch]

I guess that's not a wish list here, but #25887 (extend diff editor with merge features) has no downvote and quite a big community-request-level:

[AnrDaemon]

But I wonder if there are statistics for users, which will count the features that users most want and the bugs that they most want to fix.

When there are 4k++ open issues, it's rather hard to find the one relevant to your problem. Which makes it problematic to amass representative number of responses to any single problem.

[AnrDaemon]

I think this statistic (https://vscode-github-stats.netlify.app/) is great.

I think statistics of a moving average of opened and closed issues per 10 days would be more representative than absolute numbers.

[sanket-bhalerao]

Having that update notification on the insider's build after so long feels sooo good 🎉.

[lucastrvsn]

Any chance of #5280 to be included on this roadmap? This minor feature will allow keybinding extensions to do so much! Thanks.

[KamasamaK]

Any plans to update the yearly roadmap for 2021 in this iteration?

[demonguy]

i still wonder if we're going to have 3-way merge diff editor

[PathToLife]

@lucastrvsn
#5280 pr made #115190

[objectivecosta]

Is a macOS ARM version coming this release? I see the bullet point, but no issue #.

[LiuYiwai]

Is a macOS ARM version coming this release? I see the bullet point, but no issue #.

I think yes, I see the relevant PR in homebrew-cask.

[GitMensch]

January 29, 2021: Endgame done

vs.

The endgame details for this iteration are tracked in TBD.

Can you share an updated time for this? We all know how burdened those times are, but it likely helps some people to know more about the expected new date. If there's still much to do then it is completely fine to make it a December->January->February iteration plan, the only thing that is bad is to stay on "done end of January" when it did not started yet and is February.

[Tyriar]

@GitMensch I filled in the link: #114896, this just like our other releases have work done during the month it was named and released early the following month. Expect the release later this week, but it's possible it could get pushed to Monday.