Vscode: Iteration Plan for April 2019

[kieferrm]

This plan captures our work in April. This is a 6-week iteration. We will ship our April Update in early May. You'll notice that we list less work than usual in an iteration that is longer than usual. If you wonder what we are up to: One of the most commented issues is about WSL and led us to explore what we can do (#63155). It made us realize that with a bit of enablement in the core, we can build extensions that greatly improve the WSL experience and "a bunch of other stuff" :smiley:. It's a model comparable to what happened a year ago with the LiveShare extension. So, this month we keep the focus on those extensions and lift the curtain in early May. It's going to be cool, stay tuned.

Oh, and the Swiss part of our team needs to set a :snowman: on :fire:.

Endgame

• May 6, 2019: Endgame begins
• May 10, 2019: Endgame done

The endgame details for this iteration are tracked in https://github.com/microsoft/vscode/issues/73175.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

| Mark | Description |
| ------------------- | ------------------------------------------------- |
| :runner: | work in progress |
| :hand: | blocked task |
| :muscle: | stretch goal for this iteration |
| :red_circle: | missing issue reference |
| :large_blue_circle: | more investigation required to remove uncertainty |
| :black_circle: | under discussion within the team |

UX

• [ ] :runner: Iconography re-design https://github.com/Microsoft/vscode/issues/8017 @misolori
• [ ] :runner: Explore Extensions Management UX https://github.com/Microsoft/vscode/issues/68527 @misolori @sandy081
• [ ] :runner: Explore new VS Code icons https://github.com/Microsoft/vscode/issues/71827 @misolori

LSP

• [x] LSP support for call hierarchies PR #420 @dbaeumer
• [x] LSP support for progress reporting PR #261 @dbaeumer

JavaScript/TypeScript

• [x] Adopt TypeScript 3.4.x @mjbvz

Extension Contributions

• [x] Contributions to the Vetur extension https://github.com/vuejs/vetur/milestone/7 @octref

API

• API finalization: query
• API proposals: query

Exploration

• [x] Explore support for developing on WSL https://github.com/Microsoft/vscode/issues/63155 @alexandrudima team
• [ ] :runner: Explore supporting Electron 5.0 default renderer configuration https://github.com/Microsoft/vscode/issues/68302 @bpasero @sbatten team

---

Deferred Items

• Electron 4.0 upgrade https://github.com/Microsoft/vscode/issues/61787 @bpasero
• Explore flatting folder hierarchies in the explorer https://github.com/Microsoft/vscode/issues/41627 @isidorn @joaomoreno
• LSP support for type hierarchies PR #426 @dbaeumer

[MichaelTong]

Really excited for the tease of WSL support 😀

[beastdestroyer]

Don't forget to pin when ready! @kieferrm :)

[joewood]

I'm hoping my old issue from 2 years ago can be closed ! https://github.com/Microsoft/vscode/issues/22663

[DovydasNavickas]

I googled "endgame release date", 'cause I though it was a bit earlier than May 6, 2019. And it was.
Only then I understood that you did not take 4 days of iteration just because everyone could see the newest Avengers movie.... It's just an endgame for the iteration 😂

[Geobert]

Every month I'm hoping for a line about at least exploring tree-sitter :'(

[mtxr]

@kieferrm no plans for #50062 on horizon?

[kieferrm]

@mtxr not this iteration.

[NateLing]

Should we create a hope(wish) list?

[madzadev]

@NateLing excatly! :)

[jhpratt]

Can we please get a temporary solution to #68001? Even a dropdown to toggle the setting, as indicated in the comments.

[axetroy]

Should we create a pinned issue for Features Wish List?

Developers can vote for the features they need most.

Then consider implementing it and join into the iteration plan.

[gulshan]

The list is already there-
https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc
And everyone can vote!

[randrade23]

No plans for #45385 ? It would help make autocomplete much more robust, while extending possibilities for extension devs. @kieferrm , @mjbvz , anyone?

[MichaelTong]

What is the status of WSL supporting? The task is still not checked, so will it come to the release of this month? (Anxiously waiting 😟)

[connorshea]

@MichaelTong seems your wish was granted: https://code.visualstudio.com/blogs/2019/05/02/remote-development

[paterasMSFT]

How's endgame looking? Details page still TBD. UPDATE: details page here #73175. Thanks, @ethanrutherford.

Also, for anyone unfamiliar, WSL = Windows Subsystem for Linux.

[EthanRutherford]

It exists, but hasn't been linked yet (there's actually a link to it just a few comments above)

https://github.com/microsoft/vscode/issues/73175

[BobCu]

Be sure to target WSL2, which embeds an actual Linux kernel (4.19 to start with) into Windows (including some hardware device access), and not the initial WSL "compatibility layer" (Cygwin-like) effort.