diff --git a/doc/meetings/2025-08-21.md b/doc/meetings/2025-08-21.md new file mode 100644 index 0000000..a0c00a4 --- /dev/null +++ b/doc/meetings/2025-08-21.md @@ -0,0 +1,42 @@ +# Node.js Release WorkGroup Meeting 2025-08-21 + +## Links + +* **Recording**: https://youtu.be/pu7UjHuus3A +* **GitHub Issue**: https://github.com/nodejs/Release/issues/1117 +* **Minutes Google Doc**: https://docs.google.com/document/d/1dNBW_udrzjWQknuMX4qqf8YX9zSOLftkt8cOap9DxO0 + +## Present + +* Marco Ippolito (@marco-ippolito) +* Richard Lau (@richardlau) +* Ruy Adorno (@ruyadorno) + + +## Agenda + +### https://github.com/nodejs/node/issues/59477 + * Reminder that the cutoff for landing breaking changes is 15 Sept + * On the build group there is ongoing work to migrate from gcc to clang +### https://github.com/nodejs/node/issues/56690 + * Antoine’s old key couldn’t be used anymore as it was missing an associated id + * The README instructions now also point to our own keyring, otherwise it’s a best effort to try and keep the public keyrings up to date + * This means old releases might not be validated using keys from the public keyring + * Not sure what next steps are, maybe better documentation? + * Ultimately what we can control is our own keyring, so we should point people to use that +### https://github.com/nodejs/Release/issues/1113 + * No update this week. Please continue to contribute any comments to the issue. +### https://github.com/nodejs/Release/issues/1089 + * We need a volunteer to work on a v24.x Current release next week +### https://github.com/nodejs/Release/issues/1001 + * Antoine is working on a v22.x LTS release that should go out next week +### https://github.com/nodejs/Release/issues/855 + * Marco has prepared a v20.19.5 release and is going to be promoting it next week + +## Upcoming Meetings + +* **Node.js Project Calendar**: + +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. + +