Node.js Technical Steering Committee (TSC) Meeting 2023-10-04 #1446
Comments
|
I think we can remove nodejs/node#48740 from the agenda, the |
|
I recommend we talk about nodejs/node#49344: If you use ESM with Node.js v20 there are no solutions to reliably getting code coverage. I recommend we postpone marking |
How would that work? We delay releasing 21.0.0? Doesn’t 20 become LTS automatically when 21 is released? |
@GeoffreyBooth No it does not. The releases are independent and follow the timelines in https://github.com/nodejs/Release. On current schedules there's a 1 week period where both Node.js 21 and Node.js 20 are current releases[1]. "Current" is a description applied to a release line, it is not a singular noun. [1] A long time ago the schedules were the other way around and the even release became LTS the week before the new semver major was cut which meant a period when there was no release marked current. |
|
I think that delaying is a serious action as people make plans around the LTS dates. If we knew we'd have a fix in 1 or 2 weeks then a delay might make sense, but if it's an unknown slip I'm not so sure. |
|
If a delay is undesirable, and a fix isn't forthcoming, is a revert warranted? |
|
It seems like a V8 bug. I don't know what we could revert? |
|
It doesn't seem we have a fix in sight, and we don't know when this started (possibly caused by one of the V8 upgrades?). I think we have many other occasions where something can cause a regression and we move on with the LTS schedule - take the vm issues that are still blocking jest users from upgrading from v16 which is now EOL for example, even though we had clearer ideas what was going on and what needed to be done by V8 to fix that, and it apparently had a wide impact, we didn't block any release because they were unfixed. |
|
Also I am not sure what postponing v20 LTS is going to achieve if we have no idea how to fix it yet...I think we should only postpone LTS when it's clear that it needs some semver-major changes to fix - from the glance of the bug though I doubt if that's likely, this probably goes back to some bug in the V8 platform/task runner/garbage collector, the fix is more likely to be semver-patch and if so, we could backport it to v20 when it gets figured out. |
Semver-major changes would not normally be allowed to land on any release line (including Node.js 20) regardless of status (current, LTS, etc.). |
|
Ah, yes, then postponing LTS is less useful to unblock anything, as the branch has already been cut for the LTS. |
|
PR for minutes - #1450 |
Time
UTC Wed 04-Oct-2023 15:00 (03:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/TSC
--default-type=modulethe Node.js default #1445nodejs/admin
nodejs/socketrepository for Node.js implementation of Cloudflare's Socket API #826Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-agendaacross all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.Joining the meeting
Zoom link: https://zoom.us/j/611357642
Regular password
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: