-
Notifications
You must be signed in to change notification settings - Fork 570
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 - v20.x Maintenance LTS #855
Comments
I can't "pin issue". Github limits the pinned issues by 3. |
We could swap the pin with the v19.x one. Since v19.x is in maintenance we might decide not to do another v19.x release. |
@targos Looks like 20.1.0 is slated for release today. Can we expect it will appear on https://nodejs.org/en/download/current today as well or does it take a few days to show up there? I am awaiting this release because it should fix a bug with ESM loaders that I am running into (nodejs/node#47566) hence my curiosity about the release timeline. Thank you! |
It's unlikely. I'm aiming for a release tomorrow, May 3. |
Looks like 20.1.0 is up for download! Thank you @targos Although I think the Commits section on the Releases page got cut off: My issue of interest nodejs/node#47566 is there through the PR nodejs/node#47620 so I'm happy and ready to test. Thanks again. |
I'm moving the release to Monday next week (05 June) |
I'm sorry if this is the wrong place to ask, but is it possible to include nodejs/node#48933 in 20.6.0? It merges cleanly as of right now. |
It should be included, yeah. |
FWIW v20.6.0 might be delayed by one day (16-08-2023). @UlisesGascon is working on it. |
This comment was marked as spam.
This comment was marked as spam.
FWIW v20.6.0 is delayed until Monday (21-08-2023) because we need to run CITGM/CI/V8-CI. |
@nodejs/releasers folks, we need volunteers for the next v20.x release. Unfortunately, I can't prepare any release until the end of the month. Since we've just released v20.6.0, I'm pushing the v20.7.0 release date by a week (there are a bunch of commits already). |
In Oct I won't be available, but I am happy to take leadership or at least prepare v20.7.0 |
Anyone for a release tomorrow or later this week? |
I might be able to work on it Wed-Thu if no one else is available to pick it up 😊 |
No, due to releaser availability we weren't able to a release before LTS. The LTS transition release will be Node.js 20.9.0. |
To which resources this project release refer to? |
The ones downloadable from https://nodejs.org/. |
Can we please add
to the next 20.x release? It's blocking nodejs/node-addon-api#1409. |
Also this fix is needed: |
Could we please have nodejs/node#51801 in the next release? It will help us with our next release of Node-API. |
It will depend on timing. nodejs/node#51801 needs to go out in a current release first before being eligible for LTS, and usually be in a current release for two weeks. The next current release looks likely to be Node.js 22.0.0. |
A release was scheduled for this month I can volunteer for next week |
I can volunteer for 20.14.0 starting at the end of this week, target date 27/28 may |
I can volunteer for 20.15.0 for the week around 20th of June, if anyone else wants to do it |
If nobody else wants to I can volunteer for 10th~ of July |
@RafaelGSS Since the security release has been delayed I guess I'll move v20.16.0 2 weeks after the security release right? |
I'll prepare a release for the 1st of October |
I see that the README lists 2024-10-22 as the maintenance start date of v20, but it is still marked as LTS. So what is the current state of it? It's... unsettling to not have any LTS version at the moment. |
I opened #1048 last night to update the status. Node.js 22 will become LTS on Tuesday (29 Oct) with the 22.11.0 release -- I'll merge #1049 after that release to update the README. |
Maintenance is still LTS. |
Draft schedule - all dates subject to change
Current
The text was updated successfully, but these errors were encountered: