This plan captures our work in September. 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:

Notebooks

• Polish run by line vscode-jupyter#5607 @DavidKutu @roblourens
• Ship a reasonable full debugging experience vscode#126431 @roblourens @DavidKutu
• 🏃 Polish general workflow experience, fix papercuts and perf issues @greazer team
  • 🏃 Notebook scrolling vscode-jupyter#7360
  • Investigate ways to make Outline/Table of Contents more discoverable vscode#127200
  • Regressions from WebView or otherwise vscode-jupyter#7361
• Contribute to New File ... vscode-jupyter#7363 @IanMatthewHuff

Python Notebooks

• 🏃 Explore intellisense dissonance between interpreters and kernels vscode-jupyter#6333 @rchiodo

Interactive Window

• Polish interactive window: vscode-jupyter#7168 @joyceerhl

Documentation

• None.

Engineering

• Separate default output renders into their own web-enabled extension vscode-jupyter#1909, vscode-jupyter#6404 @DonJayamanne
• Run full test pass on Codespaces (compute and no-compute) vscode-jupyter#7592 @SiddhanthUnnithan @greazer
• 🏃 Update old webview tests to work against native vscode-jupyter#6516, vscode-jupyter#7028 @joyceerhl @rchiodo
• 🏃 Simplify Code clean-up/simplification in the Jupyter extension vscode-jupyter#6950 @DonJayamanne @rchiodo @joyceerhl
• 💪 Provide automated performance test suite vscode-jupyter#7437 @DavidKutu

Deferred

• Placeholder kernel to ensure run button appears immediately in a notebook vscode-jupyter#5861 @DonJayamanne
  • Add telemetry to get perf times for loading python & non-python kernels for the first time (without cache)