-
Notifications
You must be signed in to change notification settings - Fork 2k
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
16.0.0 Release plan #2860
Comments
Just adding my previous WIP PRs for this:
|
Referencing the original Road To TS issue for visibility: #2104 |
@IvanGoncharov How the status of TS migration? On GraphQL-JS WG we talked about creating a branch for me and @saihaj so we could join forces. |
@kamilkisiela Sorry for the delay, was moving our company to a new office 🤯 |
Thoughts on using |
@IvanGoncharov any updates? I would love to push TS forward. Maybe @saihaj could rebase on |
@kamilkisiela me and @IvanGoncharov worked on rebasing my branch yesterday and as we discussed in WG my branch will be moved hopefully by tomorrow to this repo if all goes well today. |
Is the |
Is #2839 to be included in this effort? |
@acao I believe the plan is for |
I do not see any DENO package listed on https://deno.land/x/ |
@khanakia we need to test Deno support. You can try deno branch in this repo and see if it works |
Goals
master
tomain
.Planned breaking changes
core-js
+babel
.Post 16.0.0 goals
P.S. We need to target
04/31/2021
for17.0.0
release at that point we need to do a breaking release anyway to drop Node v10.Steps
15.x.x
release line and release15.5.0
(Jan 8th)master
tomain
and update scripts & CImain
16.0.0-alpha.1
with all expected breaking changes but still from Flow sources (Jan 12th)Jan 15th)tsc
and TS-specific ESLint checks (Jan 18th)tsc
errors with@ts-ignore
and fix them in separate PRs by volunteers16.0.0-alpha.3
and gather feedback (finish until Feb WG)16.0.0-rc.1
and gather feedbacktsdoc
16.0.0
🎉17.0.0-alpha.0
branch and have a setup that will automatically release package after every merge.17.0.0
.How I can help?
The text was updated successfully, but these errors were encountered: