-
Notifications
You must be signed in to change notification settings - Fork 569
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 - v18.x Maintenance LTS #737
Comments
@juanarbol do you still plan to prepare a release for tomorrow? No worries if you can't, but I'd like to know so I take time to do it. |
@targos do you still have time to pick it up (maybe delayed until Weds/Thurs)? I reached out to @juanarbol by other means and it seems he is unavailable this week. |
I'll do it |
I'm still preparing v18.x - aiming for Thursday (8/11) release date. |
Preparing v18.x is still ongoing - right now, it seems I am blocked by backporting nodejs/node#44056 (I may try myself) because the rest of the merge conflicts/test failures build on top of that. Depending on if I can get that done in the next ~2 days, I may just work with @ruyadorno to get the giant 18.x release out next week for 8/23. |
Sounds good to me @danielleadams 👍 |
@nodejs/releasers We have a release target of 2022-09-20. However, the Security Release (v18.10.0) will be issued on 2022-09-22. Would be ok to postpone the regular release to at least 2 days after the Security Release (24/09)? That would be better for me since I'm part of both releases. |
@RafaelGSS I think we could push it back a week, or even skip this next minor release in favor of the security release. As long as commits from main get pulled in before it goes LTS, I think it's fine. |
I can't push it a week, because I won't be able to do any release after 29 (until the middle of Oct). I think I can release it on 27/09 cutting commits from 23/09. What do you think? |
@RafaelGSS oh, I see. I think that's fine because the next target date is 04/10. I can also pick it up for 27/09 if you want with all the recent commits, and then we can see if we should push the 04/10 one out 1 week too. |
Hi! Will there be a release between now and the LTS version? Would the LTS release actually only contain a version number bump commit? |
Can you update the schedule, maybe also with planned releases like the 19 release schedule? |
We will probably discuss and update the schedule in our monthly meeting next week. |
I see new version already for node 19, new version of 18 was scheduled for yesterday, so I hope 18.13 will be released soon. |
Hello @targos, |
Yes, it will be part of it. |
TODO: Re-enable these tests in Node.js v18 once the fix for this Node.js test runner bug is published in a v18 release: nodejs/node#48845 The Node.js v18.19.0 release is scheduled for 2023-11-28: nodejs/Release#737
Can we please land nodejs/node#50186 on the upcoming v18? This is a bug fix. Because of this we are unable to move to node 18 and have to use node 16. |
The Node-API team also needs nodejs/node#50991 in v18.x in order to unblock nodejs/node-addon-api#1409. Could you please add it to the upcoming v18 release? |
Hi Folks, Node.js v18 is in maintenance, implying we no longer perform scheduled releases to this release line. However, a release would only happen if one of these criteria is met:
The suggestion to all Node.js users is to upgrade to Node.js 20 as soon as possible. |
Now, that we have 18.x security release planned. can we land nodejs/node#50186 on v18 now? |
Turns out they don't apply cleanly. So, I filed a PR: |
May we please have nodejs/node#51801 in the next release? It will help us with our next Node-API release. |
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. |
If there will be another minor release of v18.x, it would be very nice to have nodejs/node#52762 included. The patch applies cleanly. |
Draft schedule - all dates subject to change
Current
The text was updated successfully, but these errors were encountered: