-
Notifications
You must be signed in to change notification settings - Fork 346
Closed
Description
This plan captures our work in February. We follow the same iteration cycle as VS Code. Although we plan for a whole iteration, we may not only ship at the end of an iteration but throughout.
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:
| Mark | Description |
|---|---|
| 🏃 | work in progress |
| ✋ | blocked task |
| 💪 | stretch goal for this iteration |
| 🔴 | missing issue reference |
| 🔵 | more investigation required to remove uncertainty |
| ⚫ | under discussion within the team |
Jupyter Notebook High Priority
- 🏃 Maintain empty list of issues labeled as an important Golden Scenario issue. @greazer team
Jupyter Notebook Focus Areas
- 🏃 Improve key kernel enumeration, selection, startup, crashing, hanging issues. vscode-jupyter#7901 @DonJayamanne
- 🏃 February iteration kernel issues: Query @DonJayamanne @greazer team
- Investigate Kernel Doctor as part of above work vscode-jupyter#5150 @DonJayamanne @greazer team
- 🏃 February milestone issues. Consists of key regressions, golden-scenario, and some polish.
- 💪 Prep and ship preview of Jupyter "Power Tools" extension. Includes prototypes, experiments, previews of things like: Scratchpad for Jupyter Notebooks, Context help for Jupyter Notebooks, Kernel Management etc. @greazer team
Upstream VS Code
- After moving builtin renderers to be regular renderers, revisit overall default renderer packaging and installation. vscode#142429
Engineering
- 🏃 Establish plan for removing package installation dependencies Jupyter has in Python (ipykernel, nbconvert, jupyter, pandas, etc). vscode-jupyter#8457 @rchiodo @brettcannon
- 🏃 Review & Document architecture, validate assumptions, plan improvements with discussion and help from Structure101 tool vscode-jupyter#8933 @greazer team @rebornix @roblourens
- 💪 Provide automated performance and test validation test suite vscode-jupyter#7437 @rchiodo and @greazer team
- 💪 Review and update old webview tests to work against native vscode-jupyter#7028 @rchiodo
- 💪 Refactoring work vscode-jupyter#6950 @DonJayamanne @rchiodo
Deferred
- 💪 Investigate requirements and create plan for extension to be web-enabled. #8664 Why Deferred? End to end story needs to be established as it may not be necessary to fully web-enable the Jupyter extension.