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.

Sign up for GitHub

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

Jump to bottom

Make it easier for extension authors to follow our extension API workflow (from proposal through finalization) #84507

Closed
eamodio opened this issue Nov 11, 2019 · 1 comment
Closed

Make it easier for extension authors to follow our extension API workflow (from proposal through finalization) #84507

eamodio opened this issue Nov 11, 2019 · 1 comment
Assignees
@eamodio @jrieken
Labels
api extensions-development Issues for developing extensions plan-item VS Code - planned item for upcoming
Milestone
November 2019

Comments

@eamodio
Copy link
Contributor

eamodio commented Nov 11, 2019

Currently it is difficult for extension authors to follow our extension API development (from proposal through finalization). We want to try to provide more clarity (transparency) around proposals and how they will (or not) become stabilized.
@eamodio eamodio added api plan-item VS Code - planned item for upcoming extensions-development Issues for developing extensions labels Nov 11, 2019
@eamodio eamodio added this to the November 2019 milestone Nov 11, 2019
@kieferrm kieferrm mentioned this issue Nov 11, 2019
Closed
68 tasks
@eamodio
Copy link
Contributor Author

eamodio commented Dec 3, 2019

I updated the Extension API Process wiki with the changes.

@eamodio eamodio closed this as completed Dec 3, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@eamodio eamodio

@jrieken jrieken

Labels
api extensions-development Issues for developing extensions plan-item VS Code - planned item for upcoming
Projects
None yet
Milestone
November 2019
Development

No branches or pull requests
2 participants
@eamodio @jrieken