|
| 1 | +# Node.js Release WorkGroup Meeting 2024-05-30 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: https://www.youtube.com/watch?v=jpz0ZhDHS8M |
| 6 | +* **GitHub Issue**: https://github.com/nodejs/Release/issues/1011 |
| 7 | +* **Minutes Google Doc**: https://docs.google.com/document/d/1McsLuKvHCRW-XYB2hKTGOADO-WO84T7QFn07PdT_woI/edit |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Ulises Gascón: @UlisesGascon |
| 12 | +* Marco Ippolito: @marco-ippolito |
| 13 | +* Richard Lau: @richardlau |
| 14 | + |
| 15 | + |
| 16 | +## Agenda |
| 17 | + |
| 18 | +## Announcements |
| 19 | + |
| 20 | +*Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. |
| 21 | + |
| 22 | +### nodejs/Release |
| 23 | + |
| 24 | +* Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004) |
| 25 | + * We discuss and agree about adding a single rule (`staging-*`) to cover this scenario for now and the future. |
| 26 | + * This will require changes in the documentation potentially (Marco will lead this) |
| 27 | +* Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001) |
| 28 | + * There are volunteers until June |
| 29 | +* Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999) |
| 30 | + * Antoine already prepared a release |
| 31 | + * Ulises to check with Ruy regarding onboarding next steps. |
| 32 | +* PGP keys verification [#965](https://github.com/nodejs/Release/issues/965) |
| 33 | + * No news from now. Reminder sent on Slack |
| 34 | +* Release plan - v21.x Current [#932](https://github.com/nodejs/Release/issues/932) |
| 35 | + * No more releases planned and it got drop from the agenda |
| 36 | +* Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) |
| 37 | + * Marco is preparing releases until June |
| 38 | +* Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) |
| 39 | + * No expectation for new releases right now, but we keep track of dependencies upgrades, as well for testing stability. |
| 40 | + |
| 41 | +### nodejs/citgm |
| 42 | + |
| 43 | +* Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060) |
| 44 | + * Brief discussion about the situation but no action pending (yet) |
| 45 | + |
| 46 | + |
| 47 | + |
| 48 | +## Q&A, Other |
| 49 | + |
| 50 | +* Let’s start thinking about Node.js@23 |
| 51 | + * Ulises want to get involved into it, but depends on his current availability in Sep/Oct |
| 52 | +* What is the current situation of the LTS team? |
| 53 | + * We made some discussion about it in the past |
| 54 | + * It has an historical context prior to the current Release team, so the organization has evolved since them. |
| 55 | + * LTS team does not provide additional access to resources (Ex. Jenkins) |
| 56 | + * Marco explained that some documentation might be outdated regarding major releases and the LTS team. |
| 57 | + * This PR seems relevant (ignoring the backporting part) https://github.com/nodejs/Release/pull/912 |
| 58 | + * Marco will open an issue about it |
| 59 | + |
| 60 | +## Upcoming Meetings |
| 61 | + |
| 62 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 63 | + |
| 64 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
| 65 | + |
0 commit comments