May Iteration Plan #6105
Description
This plan captures what we work on during May and will ship early June.
We arrived at the following themes for May:
- Work on highly requested UI features (tabs, integrated terminal).
- Make a repository with the Monaco/standalone editor available.
- Continue to do some UI explorations.
The May Test Plan items are created as issues get closed.
For more information about our development process please refer to the development process page.
Schedule
The goal is to make the May update available by the following dates.
End game dates (we end an iteration with an endgame)
Monday, May 23
- Code freeze at end of day
- Test plan input done at 9 pm Zurich time
- Prepare blog post about more frequent update of
insiderchannel
Tuesday, May 24
- Test plan ready
- Test build done
- Testing
Wednesday, May 25
- Testing
- Fixing
Thursday, May 26
- Fixing
- Run OSS tool
- Verification
- Update release notes
Friday, May 27
- Fixing (only critical bugs)
- Smoketest
- Windows - @alexandrudima
- OS X - @sandy081
- Linux - @joaomoreno
- All release notes updated
- Acknowledge pull requests in release notes - All
- All issues verified
- Satellite modules ready, version updated, smoke tested
- vscode @bpasero
- yo generator @aeschli
- vsce @joaomoreno
- node debug @weinand
Monday, May 30
- build
insiderrelease - sanity check
insiderrelease- Windows - @dbaeumer
- OS X - @joaomoreno
- linux - @weinand
- Release
insiderchannel
Monday, June 6
- build
stablerelease - sanity check
stablebuild - Release
stablechannel - Redmond
Tuesday, June 7
- Change
insiderchannel to take over role fromalpha - Retire
alphachannel
Plan Items
| Mark | Description |
|---|---|
| 🏃 | work in progress |
| ✋ | task is blocked |
| 💪 | stretch goal for this iteration |
Debt Items
This section lists items to reduce our engineering debt:
- 🏃💪 Extract the MarkDown editing support into an extension Extract the MarkDown editor into an extension #6106 @kieferrm
Feedback
Issues to address feedback from the community:
- 🏃 UI - Tabs - support stacks in editor groups, expose stacks in an
open editorspane (was working files) Proper tabs for open files #224 @bpasero @isidorn- Test Test: Editor stacks #6536
- Release notes
- UI - Add an integrated terminal Request feature "Integrated terminal" #143 @Tyriar
- Test Test integrated terminal #6654
- Release notes
- 🏃 Editor - Support that the Monaco editor can be consumed standalone @alexandrudima
- Define 1.0 version of the API
- Support to contribute new language outside of the editor source tree
- Test Test language supports refactorings #6655
- Release notes
- API - Expose the diff editor in the API Expose diffEditor to plugins #1865 @jrieken
- Test test new
vscode.diffcommand #6648 - Release notes
- Test test new
- CSS: Variables should offer same support as SASS/LESS variables [css] CSS variables should offer same support as SASS/LESS variables #3077 @sandy081
- Test Test CSS variables #6656
- Release notes
- Install - Support to install/update an extension from the command line Support to install and uninstall extensions from cli #691 @joaomoreno
- Test Test: Command line extension management #6099
- Release notes
- UI - Intellisense support to disable word completions, to address Weird auto-completion results for Azure Storage Account type #5574 @jrieken
- Test Test
editor.wordBasedSuggestionssetting #6650 - Release notes
- Test Test
- Debug - Support to start a debug session from an extension: vscode.startDebug should take debug configuration json as argument #4615 @isidorn
- Test vscode.startDebug api command #6248
- Release notes
- vscode-eslint support a "fix all" action @dbaeumer
- Test Test: ESLint fix all command #6581
- Release notes
- vscode-tslint support quick fixing of warnings same as in vscode-eslint @egamma
- Test Test Quick fix support for tslint warnings #6700
- Release notes
Engineering
This section lists several engineering/development items that the team identified:
- API - Add documentation for virtual document support and provide a sample @jrieken
- Test Test extension samples #6675
- Release notes
- JSON - Support to rewrite JSON configuration files programmatically @aeschli
- Debug - support a all "One Thread" and "All Thread" model @isidorn @weinand
- Test Threads continue event #6160
- Release notes
- Debug - Slow call stack response for TS repository Slow call stack response for TS repository #5645 @weinand
- Test Test slow variables and call stack improvements #6658
- Release notes
- Debug - Node v6 debugging support debug doesn't work on node v6 #6029 @weinand
- Test Test Node v6 debugging support #6659
- Release notes
- Debug - Introduce "Reveal" setting for debug console Setting for revealing the debug console #6159 @isidorn
- Test Setting for revealing the debug console #6159
- Release notes
- 🏃 Improve story for markers generated by a task and markers generated by a language service @dbaeumer
- See proposal here: Improve diagnostic story for build and reconcile diagnostics #6973
- Linter/language protocol support a trace option @dbaeumer
- Test Test: language server protocol trace option #6580
- Release notes
- Telemetry - Explore shared telemetry implementation with VS Support paging of stack frames #4792 @jrieken
- Test Test telemetry #6246
- Release notes
Explorations
- 🏃 UI - Improve extension installation UI Need better extension management UI #637 @joaomoreno
- 🏃 UI - Move the error list from the quick box to a panel @sandeep
Deferred from May
- Configuration - Help getting started with configuring the Code preferences @aeschli
- UI - Indent guides Indent guides #2192 @alexandrudima @aeschli
- 🏃 Debug - Debugging with babel-register (dynamic sourcemaps) + NodeJs does not work Debugging with babel-register + NodeJs does not work #5728 @weinand
- UI Open custom terminal for OS X Support custom terminal launch settings on OS X #5462 @Tyriar
- UI - Support to increase the font size used by IntelliSense Increase font size of IntelliSense #2465 @joaomoreno
Bugs
Bugs assigned to the current milestone: