Vscode-remote-release: Remote: Iteration Plan for January 2020

Created on 20 Dec 2019  路  6Comments  路  Source: microsoft/vscode-remote-release

This plan captures our work on the Remote development extensions in January. We follow the same iteration cycle as VS Code. Although we plan for a whole iteration, we 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 |
| ------------------- | ------------------------------------------------- |
| :runner: | work in progress |
| :hand: | blocked task |
| :muscle: | stretch goal for this iteration |
| :red_circle: | missing issue reference |
| :large_blue_circle: | more investigation required to remove uncertainty |
| :black_circle: | under discussion within the team |

Remote - Core

Remote - SSH

Remote - Containers

Remote - WSL

Deferred Items

iteration-plan
Source
picture kieferrm

Most helpful comment

@Chuxel We cannot help you to achieve this Roadmap faster. It Is the downside of the full closed source strategy on this extension.
So It Is totally out of our control how many resources you can allocate on this extension. We can just ask you to schedule incrementally over the most popular upvoted features.
If these are too big you can just approach incrementally as you have done with the other core features.

picture bhack on 8 Jan 2020
👍4

All 6 comments

Please give some sense to the community top upvoted priorities in containers section:
https://github.com/microsoft/vscode-remote-release/issues?q=is%3Aopen+label%3Acontainers+sort%3Areactions-%2B1-desc

bhack picture bhack on 21 Dec 2019

I have the same issue of Allow piping to stdin #1764 using Remote - SSH

imba-tjd picture imba-tjd on 24 Dec 2019

@bhack We've been away for the holidays, but now that we're back I wanted to briefly mention that the draft 2020 roadmap for VS Code was published before the holidays which includes Kubernetes investigations (along with macOS which is the top one today). See the VS Code Roadmap and Remote Roadmap drafts.

For a bit of insight, here鈥檚 a how we鈥檙e thinking about new platforms: For existing platforms, we know that lots little or medium sized issues can cause major problems for something you use every day. We don鈥檛 want to let the community down, so we want to be sure we鈥檙e in good shape on existing supported platforms before moving onto the next one. When the product is at that point is primarily driven by community feedback - particularly the 2000+ issues that have been logged here. Each platform we鈥檝e added has had its own unique challenges, even for something as consistent as SSH, and we know Kubernetes is going to be bigger change particularly given we try to cater to people running any of the three major platforms locally (Linux, macOS, and Windows). For SSH, we started with server operating systems, and containers we started with Docker - so while we haven鈥檛 picked them up quite yet, macOS and Kubernetes were explicitly called out on the roadmap given community interest.

Also, if anyone is interested in the planning process, the VS Code Remote Development extensions use the same process as VS Code. As with the microsoft/vscode repo, once we understand an issue, we watch :+1: reactions across issues to understand interest rather than individual responses due to the sheer volume of them that comes across between the two repos. We absolutely hear the feedback and definitely appreciate the upvoting - it really does help!

Chuxel picture Chuxel on 8 Jan 2020
👍2

@Chuxel We cannot help you to achieve this Roadmap faster. It Is the downside of the full closed source strategy on this extension.
So It Is totally out of our control how many resources you can allocate on this extension. We can just ask you to schedule incrementally over the most popular upvoted features.
If these are too big you can just approach incrementally as you have done with the other core features.

bhack picture bhack on 8 Jan 2020
👍4

Please add offline support for completely offline/behind firewall systems (both host and the remote) #2176
The current situation assumes, the host has access to internet but this shouldnt be. at least providing an offline package with all the dependencies would be great (just like how the cpptools extension does it)
Thank you all very much for all of this.

Coderx7 picture Coderx7 on 20 Jan 2020
👍2

Also there this one one of highest voted feature request and its fairly simple one

https://github.com/microsoft/vscode-remote-release/issues/222

Just need a option for argument

Lastwisher picture Lastwisher on 7 Feb 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

gurdevrana picture gurdevrana  路  3Comments
jkoritzinsky picture jkoritzinsky  路  3Comments
sulume picture sulume  路  3Comments
nphmuller picture nphmuller  路  3Comments
kieferrm picture kieferrm  路  3Comments