-
Notifications
You must be signed in to change notification settings - Fork 578
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
Incorrect start date in schedule.json #361
Closed
bnb opened this issue
Oct 1, 2018
· 3 comments
· May be fixed by DerekNonGeneric/wg-nodejs-release#6
Closed
Incorrect start date in schedule.json #361
bnb opened this issue
Oct 1, 2018
· 3 comments
· May be fixed by DerekNonGeneric/wg-nodejs-release#6
Comments
@jasnell, @MylesBorins can you two comment if we have a specific date to update it to yet? |
We hadn't picked a date yet. How about Tuesday October 30th? |
@jasnell can you also update the Node.js Long Term Support Schedule Calendar? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
schedule.json
file asserts that Node.js v10 is LTS today. As far as I know (?), this isn’t the case.Historically it seems we trend more toward the end of the month. If truly incorrect, would it be acceptable/more accurate to update it to the 31st and adjust down if needed? Happy to create a PR if the answer is yes.
For what it’s worth, I discovered this last night while working on node-release-lines, which uses the data from
schedule.json
rather heavily.The text was updated successfully, but these errors were encountered: