This plan captures our work in January. 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.
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 |
| β¬ |
a large work item, larger than one iteration |
Getting started
N/A
Environments
Editing
None
LSP
Terminal
Debugging
Formatting
Linting
Testing
vscode.dev
None
Documentation
Engineering
Python community
Deferred Items
This plan captures our work in January. 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.
Legend of annotations
Getting started
N/A
Environments
Create Environmentprovide a multi-select for potential requirements files to install; issue; @karthiknadigCreate Environmentprovide a multi-select for potential optional dependencies/extras to install; issue; @karthiknadigEditing
None
LSP
Terminal
conda run; issue; @karrtikrDebugging
Formatting
Linting
Testing
Run Test; issue; @eleanorjboydvscode.devNone
Documentation
Engineering
l10n.tAPI (PR is still in draft); PR; @paulacamargo25Python community
Deferred Items
Runmenus; issueVIRTUAL_ENV; issue.python-versionfor pyenv; issue; @karrtikrconda runwhen debugging (waiting on the conda team to give us the go-ahead to rely onconda runso fundamentally); @paulacamargo25venvPathandvenvFolders; issue