-
Notifications
You must be signed in to change notification settings - Fork 575
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
Release Schedule JSON #508
Comments
https://github.com/nodejs/Release/blob/master/schedule.json is canonical. The one in nodejs.org is a candiate for removal (nodejs/nodejs.org#2773) as the website builds overwrites it with the one from this repository. |
Awesome. I will update the tool to consume the one here. Is there any guarantee around this file? I would like to make sure that if changes are made we are aware and can update the tooling we provide. |
What kind of guarantees are you looking for? We do keep the file updated. Dates in the future are subject to change. Also codenames are only added to the schedule when the release becomes LTS (so, for example, |
All that is expected. The only thing I want is that if the format and location of the file change we will know about it. Obviously our tests will fail, but it would be nice to know before then I guess. |
It does not appear that there is anything further for us to do here, but please let me know if you disagree and we can reopen. |
On the package maintenance wg call today we were discussing one of our initiatives to keep users testing on up-to-date LTS lines. In this effort we wanted to standardize grammar around the lines and build tooling around it.
In that tool I loaded the schedule from where I saw it in the website repo:
https://raw.githubusercontent.com/nodejs/nodejs.org/master/source/schedule.json
But it looks like this repo
https://github.com/nodejs/Release/blob/master/schedule.json
Which is the canonical source? Can we rely on this always existing? Is there anything we need to know so we can support this long term?
The text was updated successfully, but these errors were encountered: