-
Notifications
You must be signed in to change notification settings - Fork 14
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
issues to address when Node 14 is in LTS #990
Comments
Tomorrow is 10/22/2020, labeling for developer meeting to revisit this issue. https://nodejs.org/en/about/releases/ indicates that Node 14 LTS is still schedule to start 10/27/2020. |
Let's defer discussion until next week after it is in Active LTS status. |
The release is now in Active LTS. We decided that the next step is to have all the developers update to Node 14 this week and run like that for a week and make sure that no major issues are encountered, and if all is good we will proceed to the next step, which is to upgrade it on the servers. |
I updated from v12.16.3 to v14.15.0 |
Yes, I have updated to Node 14: |
All production servers are now running node 14.15.0, so work on this issue should be able to proceed. |
From 11/12/20 dev meeting: We are going to close this issues and reprioritize and assign out the issues from #990 (comment). Closing. |
When Node 14 is in LTS (scheduled for 10/27/2020), prioritize and assign these issues:
#861
#949
#862
#947
phetsims/perennial#179
Added to "Future Reminders" in the PhET Developer Meeting doc, to be revisited on 10/22/2020.
The text was updated successfully, but these errors were encountered: