Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Staged rollout support for vscode extensions #550

Open
hyangah opened this issue Jan 6, 2023 · 1 comment
Open

Staged rollout support for vscode extensions #550

hyangah opened this issue Jan 6, 2023 · 1 comment
Assignees
Labels

Comments

@hyangah
Copy link

hyangah commented Jan 6, 2023

Originally opened as a feature request in VS Code repo (microsoft/vscode#170631)

VS Code auto-updates extensions as soon as the new versions become
available if the user does not opt out of the auto-update feature.
As an extension publisher (golang.go), we are often worried about the scale of
damage one bad release can result in.

It would be nice if extension publishers can have some control over the rollout speed.

e.g. push to ~10% for day1, ~40% for day3, release fully on day4....
We may want to roll out emergency update or critical security patch more aggressively.

Thorough testing before release, long baking time using prerelease/insider versions,
ability to unpublish problematic versions #235 all can help mitigating
the issue, but they do not completely eliminate large scale failures.

Staged rollout support is nothing new in other mobile, desktop app stores.
VS Code itself recognized the same kind of problem in microsoft/vscode#15602.
I don't know exactly how VS Code addressed this issue eventually but
I see staged rollout was also mentioned in microsoft/vscode#15602 (comment).

Extensions are important part of VS Code ecosystem. Often the quality/stability of
extensions is interpreted as that of VS Code. Staged rollout will help extension
publishers improving their extensions while limiting the potential risk that may affect
a large number of VS Code users.

@amit-kulkarni-in amit-kulkarni-in self-assigned this Jan 6, 2023
@tooltitude-support
Copy link

Would be really great to have it!

@seaniyer seaniyer assigned seaniyer and unassigned amit-kulkarni-in Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants