February Iteration Plan

[egamma]

February is our last full iteration before we start the end game for the Build 2016 milestone at the end of March.

We made good progress in the areas such as accessibility and localization, but more work needs to happen. Therefore we arrived at the following themes for February:

• Continue the work on accessibility, localization.
• Reduce adoption blockers - the item we want to tackle is support for Code Folding, the most voted for feature request, Issue Enable code folding and collapsing #105.
• Reduce the engineering debt.
• Respond to feedback and try to address as many issues as possible.

For more information about our development process please refer to the development process page.

Endgame Schedule

Monday, Feb 22

• Code freeze at end of day

Tuesday

• Test build done
• Testing

Wednesday

• Testing
• Fixing
• Omnisharp Smoke Test @weinand
• Run OSS tool @isidorn

Thursday

• Fixing
• Verification

Friday

• Fixing
• Smoketest
  • Windows @alexandrudima
  • OS X @isidorn
  • Linux @aeschli
• All release notes updated @weinand
• All issues verified
• Signing process initiated @joaomoreno Not needed, we can now sign ourselves.
• Satellite modules ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @joaomoreno: published vsce@1.2.0
  • Debug adapter @weinand
  • Language client/server @dbaeumer
  • eslint (recommended linter for JS) @dbaeumer

Monday, Feb 29

• Release insider channel

Monday, March 7

• Release stable channel

Plan Items

Mark	Description
🏃	work in progress
✋	task is blocked
💪	stretch goal for this iteration

Feedback

Issues to address feedback from the community:

• Support folding in the editor Enable code folding and collapsing #105 @aeschli
  • Test: Test code folding #2994
  • Release Notes
• Editor - Supporting ruler settings Supporting ruler settings #1673 @alexandrudima
  • Test: Editor - Supporting ruler settings #3233
  • Release Notes
• Editor - Improve tab and space insertion handling, show what tab size is guessed, support to convert tabs to space and vice versa Add option to convert tabs to spaces #1228 @isidorn
  • Test: Indentation #3234
  • Release Notes
• Editor - Add EOL option Add EOL option #2957 @alexandrudima
  • Release Notes
• UI - Provide action to "Open definition to the side" Provide action to "Open definition to the side" #2660 (see also Goto definition to the side with mouse is broken #2646) @bpasero
  • Test: UI - Provide action to "Open definition to the side" #3236
  • Release Notes
• UI - "Close all but this" context menu option for working files Feature Request: "Close all but this" context menu option for working files #2643 @bpasero
  • Test: UI - "Close all but this" context menu option for working files #3235
  • Release Notes
• UI - Support to switch to a working file from the quick box Allow to pick working files via quick open #441 @bpasero
  • Test: Test working files picker #2791
  • Release Notes
• UI - Experimental support for recommending extensions based on usage/setup @jrieken
  • Test: Test extension tips #2734
  • Release Notes
• UI - Improve the suggest widget performance IntelliSense filtering has become slow again in huge lists #1923 @joaomoreno
  • Test: UI - Improve the suggest widget performance #3237
  • Release Notes
• Debug - Failed preLaunchTask's should abort debugger launch Failed preLaunchTask's should abort debugger launch #2370 @isidorn
  • Test: preLaunchTask improvements #2940
  • Release Notes
• Debug - Support asp.net debug scenario (was Task.json shouldn't need to be manually created to build .NET projects before debugging #2263)
  • Add snippet support to tasks.json Add snippet support to tasks.json #3122 @dbaeumer
    • Test: Snippet support for tasks.json #3159
  • Offer the user to configure a task when the 'preLaunchTask' isn't found Offer the user to configure a task when the 'preLaunchTask' isn't found #3081 @isidorn
    • Test: preLaunchTask improvements #2940
    • Release Notes
• Debug/Node - Support nodemon development setup by adding support to automatically re-attach when node is restarted Attach launch configs should support to automatically re-attach #2103 @weinand
  • Test: Support nodemon development setup by adding support to automatically re-attach when node is restarted #3238
  • Release Notes
• Debug - Support 'EvaluateRequest' based data hovers Support 'EvaluateRequest' based data hovers #2012 @isidorn
  • Test: Evaluate based hover #3245
  • Release Notes
• Debug - API for extensions needs to support selection of 32-bit or 64-bit debug host Debugger API for extensions needs to support selection of 32-bit or 64-bit debug host #1696 @isidorn
  • Release Notes
• shifted Tasks - Cannot define multiple commands in tasks.json Cannot define multiple commands in tasks.json #981 @dbaeumer
• Install - Improve install experience on Linux Create .deb package for Debian-based Linux distros #2679, Shell script to install vs code in Unix systems #269 @Tyriar
  • Test: Install - Improve install experience on Linux #3239
  • Release Notes
• Launch - Improve launching on Unix based systems Code --help should show usage #378, Simplify shell command for Linux and OS X #77 @Tyriar
  • Test: Launch - Improve launching on Unix based systems #3240
  • Release Notes
• Launch - Improving launching of OS X remove need to edit the .bashrc files @joaomoreno
  • Test: Launch - Improving launching of OS X remove need to edit the .bashrc files #3241
  • Release Notesd

Debt Items

This section lists items to reduce our engineering debt:

• TSLint adoption
  • clean lint warnings Adopt tslint in our development #2102 @ALL
  • run tslint checks during pre-commit @egamma

Adoptions

We continuously have to adopt components which we require:

• ✋ Adopt the latest electron 0.36.7 @bpasero
  • Blocked due to Electron 0.36.7: SIGSEGV in forked process electron/electron#4299
• TS
  • 1.8 @dbaeumer
    • Test
  • 1.8.2 (will be available Feb 22nd) @joaomoreno
  • Release Notes (we should mention that we now include 1.8.2)

Engineering Items

This section lists several engineering/development items that the team identified:

• JavaScript - Salsa migration
  • Make Salsa the default JavaScript support and guide users to the release notes JS - actively inform user that the JS support has changed and point to the change notes #3080 @dbaeumer, @egamma
  • Test: Test Salsa as the default JS infrastructure #3170
  • Release Notes @egamma
• C# unbundling
  • guide user to install the separate extension @jrieken
  • unbundle OmniSharp Remove Omnisharp from the core product #3167 @joaomoreno
  • Test: Test omnisharp installation hint #2701
  • Release Notes @chrisdias
• Install update - Improve extension selection performance Test new Marketplace API #2621 @joaomoreno
  • Test: Install update - Improve extension selection performance #3242
  • Release Notes
• Install update - No progress/status while downloading an extension No progress/status while downloading an extension #2835 @joaomoreno
  • Test: Install update - No progress/status while downloading an extension #3243
  • Release Notes
• Install update - Always install a compatible version of the extension if possible Question: How to support both 0.10.7-insider and 0.10.8 with same package? #2894 @joaomoreno
  • Test: Install update - Always install a compatible version of the extension if possible #3244
  • Release Notes
• Telemetry - provide option to opt out of telemetry @sofianhn
  • Test: Telemetry opt-out #3182
  • Release Notes @joaomoreno
• Telemetry - Gather metrics on Linux distribution Gather metrics on Linux distribution #2690 @sofianhn
• Telemetry - create a common module for 'first party' extensions @sofianhn
  • Test: Telemetry application insights refactor #3181
  • Release Notes? @sofianhn
    • @joaomoreno: I have no idea what this is, neither what I should put in the release notes. The test plan item seems irrelevant to the task description.
• Debug - expose the Trace feature for node debug surface the TRACE feature of node-debug #2609 @weinand
  • Test
• Debug - support function breakpoints in protocol Support function breakpoints in protocol vscode-node-debug#35 @weinand
  • Test: Function breakpoints #2832
  • Release Notes @weinand
• Debug - Remove mono-debug from VS Code and move it to market place, and assist users in installing it from there remove mono-debug from VS Code and move it to market place #2668 @weinand
  • Test: Test mono-debug installation hint #2831
  • Release Notes
• Keyboard accessibility Accessibility #2108 @bpasero
  • Test: Keyboard accessibility #3246
  • Release Notes
• Accessible Debugging Accessible Debugging #2671 @isidorn
  • Test: Debug accessibillity #2941
  • Release Notes
• Screen reading Screen reading #3058 @alexandrudima
  • Test: Screen reading #3247
  • Release Notes
• Localization Localize Code #2041 @dbaeumer, @weinand
  • Test: nls support for package.json and common-js #3156
  • Release Notes
• 💪 High Contrast support High Contrast Support #2711 Enabling high contrast dark theme on all platforms + hc-dark improvements #3184 @bgashler1
  • Test: High Contrast support #3248
  • Release Notes @joaomoreno
• Doc: add new contents based on community blogs @gregvanl
  • Release Notes @gregvanl

Testers

• @joaomoreno
• @isidorn
• @weinand
• @alexandrudima
• @aeschli
• @seanmcbreen
• @chrisdias (from Wednesday only)
• @stevencl
• @Tyriar
• @bgashler1 (a little bit)
• @gregvanl

[profiler-bg]

I'm confused by all the January mentions. Feb schedule should be end of Feb, should it not? Is it due to using the Jan file as template?

[chrisdias]

@profiler-bg yes, this is a work in progress :)

[piyushchauhan2011]

👍

[gilvandovieira]

👍 thanks

[zethon]

#VisualCodeFolding

[brennanMKE]

I cannot wait for code folding. I have been working heavily in VS Code over the past month and with large source files it is so helpful to collapse code to make it more readable.

[StfBauer]

👍

[nyn3x]

👍

[BazIdle]

Not sure if I should address this here, but:
Any plans on adopting new stuff from OmniSharp ?

OmniSharp crashes are still present for me in the latest (recent, "January"-one) build.

As far as I understand (from OmniSharp issuetracker), they had a lot of major changes recently.

Would love to know an insight ;)

[leeroya]

Brilliant Thanks. cant wait.

[egamma]

@BazIdle OmniSharp will continue to move forward and it is now in the best hands (the team that also works on Roslyn). The work on Omnisharp for vscode is now tracked in https://github.com/OmniSharp/omnisharp-vscode.

Your issue from above is now also tracked there OmniSharp/omnisharp-roslyn#371.

FYI @DustinCampbell

[BazIdle]

@egamma Thanks for the info

[Figbash]

@egamma @BazIdle Sorry for bugging you here, but I and many people I know have been struggling with this issue since .10.3, is there any chance someone would be willing to look at it for this iteration? I have multiple projects that do it and would love to help someone track it down. There doesn't seem to be any interest in omnisharp-vscode, our issues have been there since December with no chatter. VSCode cannot be used for us in this state, and I really want to be able to upgrade!
dotnet/vscode-csharp#6 this is my bug for the same issue.

[DustinCampbell]

Sorry @Figbash for not commenting over at dotnet/vscode-csharp#6. We're in the middle of a bunch of work to move the extension to a new version of OmniSharp that's also in progress. Once we get over that hurdle, I'll dig deeper into your issue.

[Figbash]

@DustinCampbell Thank you for letting me know. No worries about commenting I just wanted to make sure it wasn't lost in the shuffle.

[Nimzozo]

☕

[penguin020]

This is just great that you make this so transparent. Thanks.