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
Tuesday, Apr 26
Wednesday, Apr 27
Thursday, Apr 28
Friday, Apr 29
Monday, May 2
Monday, May 9
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:
Issues to address feedback from the community:
Engineering
This section lists several engineering/development items that the team identified:
Initial investigations/explorations
Deferred from April
Deferred to May
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.
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:
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
Tuesday, Apr 26
insiderchannelWednesday, Apr 27
Thursday, Apr 28
Friday, Apr 29
Monday, May 2
insiderchannelMonday, May 9
stablechannelPlan Items
Debt Items
This section lists items to reduce our engineering debt:
Feedback
Issues to address feedback from the community:
Feature request: Add support for line and column numbers in the Go To File feature #4650 Benjamin Pasero (@bpasero)
Engineering
This section lists several engineering/development items that the team identified:
Support inspecting large data structures without timeouts on 4.x versions of node.js vscode-node-debug#11 Andre Weinand (@weinand)
undefinedvscode-node-debug#14 Andre Weinand (@weinand)Initial investigations/explorations
Deferred from April
Deferred to May
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.