Remote: Iteration Plan for June 2022

[kieferrm]

This plan captures our work in June. 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
⬛	a large work item, larger than one iteration

Core

• None.

Remote-SSH

• None.

Remote-Container

• None.

Dev Container Specification / CLI

• Prepare Dev Container Spec for release devcontainers/spec#30 @bamurtaugh @chrmarti
• 💪 Replace old devcontainer CLI with new CLI in path vscode-remote-release#6859 @chrmarti
• Support for multi-platform builds devcontainers#24 @chrmarti
• 🏃 Discuss community contribution plans devcontainers/spec/pull#40 @bamurtaugh @chrmarti

Remote-WSL

• None.

---

Deferred

• Add code CLI argument to open folder in container using remote containers extension vscode-remote-release#6771 @chrmarti
• Move dev container json schema out of vscode repo and publish/consume it via schemastore.org devcontainers/spec#14 @chrmarti

[bhack]

It would be really great if we could improve the docker context change experience and it is currently quite a pain. See #6576 and #5420

[joshspicer]

Move dev container json schema out of vscode repo and publish/consume it via schemastore.org @chrmarti

We should also publish the schema for devcontainer-feature.json, as we're getting close to accepting the initial proposal (https://github.com/devcontainers/spec/blob/main/proposals/devcontainer-features.md#devcontainer-featurejson-properties). This will assist/welcome community members to author their own features.

If there is an approval process with schemastore.org, perhaps it makes sense to batch our submissions.