Skip to content
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

Iteration Plan for April 2019 #71830

Closed
5 of 9 tasks
kieferrm opened this issue Apr 5, 2019 · 18 comments
Closed
5 of 9 tasks

Iteration Plan for April 2019 #71830

kieferrm opened this issue Apr 5, 2019 · 18 comments
Assignees
Milestone

Comments

@kieferrm
Copy link
Member

@kieferrm kieferrm commented Apr 5, 2019

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" 😃. 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 on 🔥.

Endgame

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

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

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

UX

LSP

JavaScript/TypeScript

  • Adopt TypeScript 3.4.x @mjbvz

Extension Contributions

API

Exploration


Deferred Items

@kieferrm kieferrm added this to the April 2019 milestone Apr 5, 2019
@kieferrm kieferrm pinned this issue Apr 5, 2019
@kieferrm kieferrm changed the title Iteration Plan for April 2019 Iteration Plan for April 2019 [DRAFT] Apr 5, 2019
@MichaelTong
Copy link

@MichaelTong MichaelTong commented Apr 8, 2019

Really excited for the tease of WSL support 😀

@chpxu
Copy link

@chpxu chpxu commented Apr 8, 2019

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

@joewood
Copy link

@joewood joewood commented Apr 8, 2019

I'm hoping my old issue from 2 years ago can be closed ! #22663

@DovydasNavickas
Copy link

@DovydasNavickas DovydasNavickas commented Apr 9, 2019

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 😂

@kieferrm kieferrm changed the title Iteration Plan for April 2019 [DRAFT] Iteration Plan for April 2019 Apr 9, 2019
@Geobert
Copy link

@Geobert Geobert commented Apr 9, 2019

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

@mtxr
Copy link

@mtxr mtxr commented Apr 11, 2019

@kieferrm no plans for #50062 on horizon?

@kieferrm
Copy link
Member Author

@kieferrm kieferrm commented Apr 11, 2019

@mtxr not this iteration.

@NateLing
Copy link

@NateLing NateLing commented Apr 12, 2019

Should we create a hope(wish) list?

@madzadev
Copy link

@madzadev madzadev commented Apr 15, 2019

@NateLing excatly! :)

@jhpratt
Copy link

@jhpratt jhpratt commented Apr 18, 2019

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

@axetroy
Copy link
Contributor

@axetroy axetroy commented Apr 19, 2019

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
Copy link

@gulshan gulshan commented Apr 19, 2019

@randrade23
Copy link

@randrade23 randrade23 commented Apr 29, 2019

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

@MichaelTong
Copy link

@MichaelTong MichaelTong commented May 2, 2019

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
Copy link
Contributor

@connorshea connorshea commented May 2, 2019

@paterasMSFT
Copy link
Member

@paterasMSFT paterasMSFT commented May 8, 2019

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
Copy link

@EthanRutherford EthanRutherford commented May 8, 2019

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

#73175

@BobCu
Copy link

@BobCu BobCu commented May 10, 2019

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.

@kieferrm kieferrm closed this May 20, 2019
@kieferrm kieferrm unpinned this issue May 20, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet