-
Notifications
You must be signed in to change notification settings - Fork 555
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 plan - v19.x Maintenance #793
Comments
I would recommend we avoid this week due to nodejs/build#3028 (comment). Maybe with the delay for nodejs/node#45269 we bump all subsequent dates following on from the rescheduled date? |
It looks like v19.1.0 is already out, I'll update the dates and that pushes v19.2.0 to the planned 11-29 slot. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
@targos heads up we're updating the time for the next regular v19.x release since there's a Security Release coming up the same day it was planned for your next release. |
I won't be able to perform the v19.8.0 release this week, so I've switched with @targos (I will publish v19.9.0 and Michael v19.8.0). He will be able to do it next week. So, I will adjust the dates according to it. |
I think .10's release date could be moved to .11's date and that one can be pushed even further. |
Node.js 20 is out. |
v19.x is now end-of-life. |
Draft schedule - all dates subject to change
The text was updated successfully, but these errors were encountered: