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

Q1 2021 roadmap #8824

Closed
15 of 22 tasks
bartlomieju opened this issue Dec 18, 2020 · 12 comments
Closed
15 of 22 tasks

Q1 2021 roadmap #8824

bartlomieju opened this issue Dec 18, 2020 · 12 comments
Labels
cli related to cli/ dir

Comments

@bartlomieju
Copy link
Member

bartlomieju commented Dec 18, 2020

Roadmap Q1 2021

Scheduled releases:

  • 1.7.0 - January, 19th
  • 1.8.0 - March, 2nd

planned features and refactors:

maybe:

@bartlomieju bartlomieju added the user feedback wanted feedback from the community is desired label Dec 18, 2020
@bartlomieju bartlomieju pinned this issue Dec 18, 2020
@yos1p
Copy link
Contributor

yos1p commented Dec 19, 2020

+1 on HTTP2 support

@newtack
Copy link

newtack commented Dec 19, 2020

Ensuring deno lsp and VSCode work seamlessly?

@kitsonk
Copy link
Contributor

kitsonk commented Dec 20, 2020

Ensuring deno lsp and VSCode work seamlessly?

There will be continued work on the lsp, we just didn't know exactly what features.

@jveres

This comment has been minimized.

@Soremwar
Copy link
Contributor

@jveres SWC bugs are tracked in the SWC repo, where "real world code" is seemingly now a part of the tests for the latest refactor swc-project/swc#1264

@leoc11
Copy link
Contributor

leoc11 commented Jan 1, 2021

+1 V8 Fast API for ops

@kitsonk
Copy link
Contributor

kitsonk commented Jan 3, 2021

I have seen a bit of mis-understanding going on in issues... To be clear, these issue are to broadcast what the core team's priorities are for the quarter, and all of these will be worked on by the core team. If you want to help out, feel free to provide input.

If you want to contribute to Deno though, it is best to look at resolving issues that are not on this list. If it is any sort of significant feature, it is best to get consensus and alignment from the core team before you start on the feature, as without that feedback it will likely only lead to significant delays or even abandonment of your work. The best way to get that feedback is on the issue itself.

At the moment, the core team consists of:

There are several other long term contributors who can give you advice and suggestions as well.

@devalexqt

This comment has been minimized.

@fanweixiao

This comment has been minimized.

@StEvUgnIn

This comment has been minimized.

@kitsonk
Copy link
Contributor

kitsonk commented Jan 22, 2021

This isn't the place to put random comments about a wish list. This is an issue to communicate what the core team is working on. Other suggestions should be made in their own issue or discussions, and with more detail than a couple words.

@denoland denoland locked and limited conversation to collaborators Jan 22, 2021
@kitsonk kitsonk removed the user feedback wanted feedback from the community is desired label Jan 27, 2021
@ry ry unpinned this issue May 7, 2021
@lucacasonato lucacasonato added the cli related to cli/ dir label Jun 8, 2021
@bartlomieju
Copy link
Member Author

Q1 is long gone and relevant issues have been rolled to Q3 roadmap.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cli related to cli/ dir
Projects
None yet
Development

No branches or pull requests