Description
While watching the community feedback on 1.0, we have already started to work on the next update. We will continue to ship monthly. This plan captures what we work on during April and will ship early May.
We arrived at the following themes for April:
- Ramp up the work on the next major version.
- Do some explorations.
- Reduce engineering debt in vscode and the primary extensions which the team maintains (vscode-eslint, vscode-jshint, vscode-tslint, vscode-jscs).
For more information about our development process please refer to the development process page.
The April Test Plan is in progress.
Schedule
The goal is to make the April update available by the following dates.
End game dates (we end an iteration with an endgame)
Monday, Apr 25
- Code freeze at end of day
Tuesday, Apr 26
- Test build done
- Testing
- Push to
insider
channel
Wednesday, Apr 27
- Testing
- Fixing
- Run OSS tool
Thursday, Apr 28
- Fixing
- Verification
Friday, Apr 29
- Fixing
- Smoketest
- All release notes updated
- Acknowledge pull requests in release notes: @bpasero
- All issues verified
- Satellite modules ready, version updated, smoke tested
- vscode @bpasero
- yo generator @aeschli
- vsce @joaomoreno
- Debug adapter @weinand
Monday, May 2
- Push to
insider
channel
Monday, May 9
- Release
stable
channel
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:
- Community: Support Pull Requests for the Wiki @Tyriar
Feedback
Issues to address feedback from the community:
- UI: Start implementing support for tabs Proper tabs for open files #224 @bpasero
- UI:
Feature request: Add support for line and column numbers in the Go To File feature #4650 @bpasero - UI: Add command to reopen last closed editor Provide command to open most recently closed file/editor #3989 @Tyriar
- Test Test: Provide command to open most recently closed file/editor #5586
- Release notes
- I18N: Command palette match support for non-ascii characters Command palette's camel case matching does not work for non ASCII characters #4691 @bpasero
- Provide an option to stop scrolling revealing active file in explorer Provide an option to stop scrolling revealing active file in explorer #3062 @bpasero
- Emmet: support to disable expansion on TAB Emmet: support to disable expansion on TAB #5756 @egamma
- I18N: Support to filter the Command Palette by English name Don't localize command names on the command palette #4679 @bpasero
- API: Add support for internal links in previewHtml Add support for internal links in previewHtml #3676 @jrieken
- API: Provide API to open a new folder Provide API to open a new folder #58 @bpasero
- Git: Commit in the command palette Feature Request: Need a Git Commit command in the Command Palette #4471 @joaomoreno
- Linux: Support running vscode with sudo permissions running vscode with gksudo or sudo permission #3068 @Tyriar
- Test Test: running vscode with gksudo or sudo permission #5062
- Release notes
- Linux: Include CLI in Linux zip archive and support custom install locations Include CLI in Linux zip archive and support custom install locations #4426 @Tyriar
- Linux: Notify user when a new update is available @joaomoreno
- Debug - Data inspection support for ES6 objects (sets, maps, generators) Allow to see the entries of ES6 Map and Set vscode-node-debug#51, ES2015 iterator object of the generator has undefined value in watch vscode-node-debug#41 @weinand
- Test Data inspection support for ES6 Sets, Maps, and Generators #4949
- Release notes
- Address feedback received on primary extensions
- eslint @dbaeumer
- Test: Test: ESLint autofix #5654
- tslint @egamma
- Test: Test TS lint new features #5758
- jshint @kieferrm
- Test: Test JSHint new features #5759
- jscs: @chrisdias
Engineering
This section lists several engineering/development items that the team identified:
- Debug - Paging support for stack frames Support paging of stack frames #4792 @weinand @isidorn
- Test Test: Stack frame paging #4819
- Release notes
- Debug - Data inspection of large objects for Node v4.x and v5.x
- Test: Support inspecting large data structures on 4.x and 5.x versions of node.js #4951
Support inspecting large data structures without timeouts on 4.x versions of node.js vscode-node-debug#11 @weinand - Test Support inspecting large data structures on 4.x and 5.x versions of node.js #4951
- Release notes
- Test: Support inspecting large data structures on 4.x and 5.x versions of node.js #4951
- Debug - Data inspection support for large strings and objects with getters debugger shows javascript object properties with getters as
undefined
vscode-node-debug#14 @weinand- Tests String truncation limit lifted to 10000 #4952, Getter support #4957
- Release notes
- Implement version 2 of the language service protocol addressing feedback from version 1 @dbaeumer
- Adopt - Electron 0.37.x Update to Electron 0.37.x #4199 @bpasero
Initial investigations/explorations
- 🏃 UI - Improve extension installation UI Need better extension management UI #637 @joaomoreno
- 🏃 UI - Add an integrated terminal Request feature "Integrated terminal" #143 @Tyriar
- Debug - C++ debug scenario to enable additional debug views (e.g. memory view) @isidorn
- Debug - Support skipping code when stepping Step Into (F11) steps into transpiled JavaScript when debugging TypeScript that uses async/await #4798 @weinand
- Test Test: Support skipping code when stepping #4954
- Release notes
- API - Use web view for html preview part Use web view for html preview part #2414 @jrieken
- Test: Test previewHtml #5748
Deferred from April
Deferred to May
- 🏃 Debug - Support for dynamically generated source maps Feature request : add in code 'debugger;' to breakpoints panel for .ts and .js files #4492 @weinand
- recent change of SystemJS broke dynamic source map support; deferred to May release
- Test Support for dynamically generated JavaScript and source maps #4953
- Release notes
Bugs
This section includes bug queries for the vscode related repositories:
For more information about our development process please refer to the development process page.