You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plan captures our work in November. This is a 5 week iteration. We will ship early December.
With Version 1.18 we made multi-root-folder workspaces available to everyone and we released plenty new functionality such as viewing diffs right in the editor, and we transitioned from Nemo to Dory 😉. We also improved performance with predictably shorter startup times on Windows and optimizations of how we handle a large number of editor decorations. The performance work doesn't come as a surprise to you if you had a look at our updated roadmap.
In this iteration we'll turn the dial more toward performance and github issues housekeeping. As a consequence you will find several performance explorations and engineering items on the plan. As you know a series of feature-rich releases always takes a toll on how much we can stay atop of all of our github issues. So, if all of a sudden you see a lot of github notification, don't get scared.
Bottom line, you won't see a lot of new features in 1.19 but you'll still get a better version of VS Code.
December 11 - 22 will not be covered by a separate plan. A couple of items are at the bottom of this plan. Our January iteration starts on January 2nd, 2018.
Endgame
December 4th: Code freeze for the endgame
December 8th: Endgame done
The endgame details for this iteration are tracked in November Endgame #39540.
Plan Items
Below is a summary of the top level plan items. Given the large number of explorations, we'll diverge from our usual practice of having plan items for all bullets upfront. This time we'll add them as we go.
Legend of annotations:
Mark
Description
🏃
work in progress
✋
blocked task
💪
stretch goal for this iteration
🔵
more details required
🔴
missing issue reference
Performance
🏃 Address collected startup performance issues (see query) Team @Microsoft/vscode
Explore reordering of activities to improve startup time
@albertosantini currently the spawned processes are spawned using the node that is part of electron. This helps to avoid shipping a separate node.js version with the product. This saves around 5-6MB. This plan item investigates the benefits of giving up on using electron's version of node.
Any issue open addressing Node.js 8.x adoption?
Since we ship the node version that is part of Electron the issue to adopt version 8 .x of node.js would be in the Electron repository not in this one.
This plan captures our work in November. This is a 5 week iteration. We will ship early December.
With Version 1.18 we made multi-root-folder workspaces available to everyone and we released plenty new functionality such as viewing diffs right in the editor, and we transitioned from Nemo to Dory 😉. We also improved performance with predictably shorter startup times on Windows and optimizations of how we handle a large number of editor decorations. The performance work doesn't come as a surprise to you if you had a look at our updated roadmap.
In this iteration we'll turn the dial more toward performance and github issues housekeeping. As a consequence you will find several performance explorations and engineering items on the plan. As you know a series of feature-rich releases always takes a toll on how much we can stay atop of all of our github issues. So, if all of a sudden you see a lot of github notification, don't get scared.
Bottom line, you won't see a lot of new features in 1.19 but you'll still get a better version of VS Code.
December 11 - 22 will not be covered by a separate plan. A couple of items are at the bottom of this plan. Our January iteration starts on January 2nd, 2018.
Endgame
The endgame details for this iteration are tracked in November Endgame #39540.
Plan Items
Below is a summary of the top level plan items. Given the large number of explorations, we'll diverge from our usual practice of having plan items for all bullets upfront. This time we'll add them as we go.
Legend of annotations:
Performance
package.json
files of installed extensions Cache extension manifest files #28331 @alexandrudima @sandy081GitHub Issue Housekeeping
Serviceability
CodeHelper
process (experimental 'Processes' extension) @weinandLanguage Server Protocol
Debug Adapter Protocol
Engineering
Documentation
Deferred
December 11 - 22
Serviceability
The text was updated successfully, but these errors were encountered: