January Iteration Plan

[egamma]

We are back from the holidays and are rolling again. We are starting to target our next important milestone for Code, the Build 2016 conference, which takes place at end of March in San Francisco. The roadmap outlines our high level plans for getting there and this is our detailed plan for the January 2016 iteration.

We plan to declare General Availability ("GA") with the March 2016 release. GA comes with several quality obligations in areas such as accessibility and localization. We know that we have significant gaps here and we want to start to tackle them right away. On the drive to Connect(); we accumulated engineering debt that we must to address sooner rather than later. And, as we always do, we will continue to ship monthly and address key development pain points and adoption blockers.

Based on these imperatives we arrived at the following themes for January:

• Ramp up the work to get to GA (accessibility, localization, ...).
• Reduce the engineering debt.
• Respond to feedback and try to address as many issues as possible.

The January Test Plan is in progress.

Schedule

The goal is to make the January update available by the following dates.

End game dates (we end an iteration with an endgame)

• Monday Jan 25th evening (GMT+1): freeze
• Tuesday: test day
• Wednesday: fix day
• Thursday: fix day
• Friday: Done: documentation, release notes update, bugs verified

⚠️ update we will switch to dev channels and deprecate the insider channel. We will make the new dev channels available as soon as possible during the end game and will hold back updating the stable channel until we have received early feedback.

Plan Items

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

Feedback
Issues to address feedback from the community:

• UI: Improve auto save behaviour, support to customize auto save delay, support to save on focus lost @bpasero
  • Issues Save on focus lost #353, Add delay to autosave #1055, Allow to configure auto save per workspace #1211
  • Test Auto save settings #1854
  • Release notes
• UI: Support to hide the menu bar @bpasero
  • Issues Windows: There should be an option to hide the menu bar. #945, Add support for hiding the menu bar also on Linux  #1563
  • Test Hide the menu bar #2226
  • Release notes
• UI: Intellisense - no way to show full documentation for a completion proposal @joaomoreno
  • Test Intellisense: full documentation #2230
  • Release notes
• Editor: Support ligatures Add support for font ligatures #192 @alexandrudima
  • Release notes @jrieken
• UI: More colorful default Dark and Lite themes @aeschli
  • Issue [themes] Dark theme in 0.10.5 less colorful than in 0.10.3 #1470, [themes] More colorful default theme - Feedback #1849
  • Test Test more colorful default theme #2256
  • Release notes
• UI: Find widget improvements find widget should show x of y find results #1999 move find widget's match counter to a better spot #2033 Accessibility: Tab focus moves into hidden find widget #2010 Find Widget tab order #1869
  • Test Find Widget tab order #1869
  • Release notes
• UI: new welcome page experience Remove static welcome page and move welcome experience to the website #2166 @sofianhn
  • Test Welcome page in the website #2251
• Debug: Generalize debug adapter protocol to support other debuggers like XDebug @weinand
  • How can a debug adapter know if VS Code has finished sending all breakpoints? vscode-debugadapter-node#4
  • Feature negotiation between debug adapters and Code vscode-debugadapter-node#9
  • add an "origin" attribute to the debug protocol's "Source" type vscode-debugadapter-node#5
  • Test Source maps with inlined source #2183
  • Release notes
• Debug; Indicate changed values in Variables pane
  • Issue Debugger variables UI should highlight changed variable values #866
  • Test Changed values indication in variables pane #2171
  • Release notes
• Debug; Support conditional break points @isidorn, @weinand
  • Issue Add Breakpoint Conditions #1582, support conditional breakpoints vscode-debugadapter-node#6
  • Test Conditional breakpoints #1830
  • Release notes
• Debug: support to remote debug node running inside a docker container
  • improve source path matching (improve source path matching #1591) @weinand
  • support "address" attribute on "attach" launch config (support "address" attribute on "attach" launch config vscode-node-debug#32) @weinand
  • Test Improved support for remote node debugging #2188
  • Release notes
• API: Support to create a TextDocument virtually @jrieken
  • Issue Supporting creating a new document virtually #272
  • Test Test virtual document provider API #2007
  • Release notes
• API: Richer quick pick support @jrieken
  • Issue: rich quick pick #1795
  • Test Test quick pick enhancements #2008
  • Release notes
• API: command to preview html document (API for extensions previewing in HTML #1308) @jrieken
  • Test Test html preview command #2099
  • Release notes
• API: Allow to map a filename to a language based on a prefix (Allow to map a filename to a language based on a prefix #1851) @jrieken
  • Test Test new filename mappings #2238
  • Release notes
• API: Provide API to current editor column Provide access to current editor column #1835
  • Test Test TextEditor.viewColumn #2152
  • Release notes
• API: Support Markdown in the API (MarkedString)
  • Test Test MarkedString and MD rendering #2222
  • Release notes
• IntelliSense filtering has become slow again in huge lists IntelliSense filtering has become slow again in huge lists #1923 @joaomoreno
  • Test Intellisense optimisations #2254
  • Release notes

Debt Items
This section lists items to reduce our engineering debt:

• Start to migrate 'built-in' language services into extensions
  • Migrate JSON into an extension @aeschli
  • Test Test JSON language as extension #2257
  • Release notes
  • Deferred - Provide JSON language service in standalone monaco editor @aeschli @alexandrudima
• Deferred - Intellisense for asp.net 5 package dependencies in the project.json is currently hard coded into JSON language, Enable that this can be contributed by the C# extension.
• Debug: Provide a test suite for debugger adapters @weinand
  • Release notes
• Extensions: Separate the vscode related tools from the vscode API into the existing vscode module Proposal for separating the vscode tools from the vscode API #970 @bpasero
  • Currently the vscode node module combines the tools and the vscode API into one unit, we want to decouple the API from the used modules.
  • Test Extensions API consumption #1881
  • Release notes

Adoptions
We continuously have to adopt components which we require:

• Adopt electron 0.35.6 @bpasero
  • Issues: Windows 7: Deleting always fails with error message #1485
  • Release notes
• Deferred - TS 1.8 isn't available yet Adopt TypeScript 1.8
  • 1.8Beta is planned for Jan 25th Adopt TypeScript 1.7 #836 @dbaeumer
  • Update the vscode-extension yo generator to depend on 1.8 @bpasero
• not for January release Adopt the a newer version of OmniSharp @jrieken

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

• JS: Salsa support for JS and provide feedback @jrieken @egamma @dbaeumer
  • Test Test Salsa #2218
  • Release Notes
• UI: Support that the debug output and task output is shown in a horizontal bar Position the output window and debug console in a horizontal panel #1875 @isidorn
  • Tests Horizontal panel - output and repl #2176, Horizontal panel - general #2173
  • Release Notes
• Debug: Improve the value hover for rich objects by using the tree widget @isidorn
  • Test Debug hover complex inspection #1832
  • Release Notes
• Debug: support source maps with inlined source
  • Issues: loop complete Source objects through debugger UI  #1793, Support source maps with inlined source vscode-node-debug#27
  • Test Source maps with inlined source #2183
  • Release Notes
• ✋ Build: Automated Mac build signing @joaomoreno
• Install: Support side-by-side installs of VS Code from different channels (insider, stable) @joaomoreno, @bpasero
  • Test done by selfhost
• Enable tslint for vscode Adopt tslint in our development #2102 @egamma
  • Test - covered by dog fooding

Initial Investigations

• 🏃 Keyboard accessibility Accessibility #2108 @bpasero
  • Test Keyboard accessibility and focus indication #2145
  • Release Notes
• 🏃 Screen reading support in the editors @alexandrudima
  • Test Screen reader in editor #2258
  • Release Notes
• 🏃 Localization: investigate into localizing Code Localize Code #2041 @dbaeumer
  • Test Test localization Support #2228
  • Release Notes

Bugs

This section includes bug queries for the vscode related repositories:

• vscode

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