|
| 1 | +# Node.js Release WorkGroup Meeting 2024-06-27 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: https://www.youtube.com/watch?v=DVjoz044Y8I |
| 6 | +* **GitHub Issue**: https://github.com/nodejs/Release/issues/1021 |
| 7 | +* **Minutes Google Doc**: https://docs.google.com/document/d/1DMNQWELamC4dY3vk1Q78aLXpcoDAnOCa2CQBx5zjmHU/edit |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Release team: @nodejs/release |
| 12 | +* LTS team: @nodejs/lts |
| 13 | +* Ulises Gascon: @UlisesGascon |
| 14 | +* Richard Lau: @richardlau |
| 15 | +* Rafael Gonzaga: @RafaelGSS |
| 16 | +* Ruy Adorno: @ruyadorno |
| 17 | +* Chemi Atlow: @atlowChemi |
| 18 | +* Antoine du Hamel: @aduh95 |
| 19 | + |
| 20 | +## Agenda |
| 21 | + |
| 22 | +## Announcements |
| 23 | + |
| 24 | +* Security release coming soon |
| 25 | +* Potential changes in the process for doing releases due the security automation |
| 26 | +* There was an issue with the MacOS machines in the CI, that seems to be solved now |
| 27 | + |
| 28 | +### nodejs/Release |
| 29 | + |
| 30 | +* Current status of LTS group/ backporters [#1012](https://github.com/nodejs/Release/issues/1012) |
| 31 | + * Let’s keep it in the agenda for the next meeting |
| 32 | +* Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004) |
| 33 | + * Waiting for a PR on documentation change: https://github.com/nodejs/Release/issues/1004#issuecomment-2139671245 |
| 34 | + * Antoine suggested an alternative approach that is more friendly to onboarding new releasers by forcing sign commits rather than a branch rule.https://github.com/nodejs/Release/issues/1004#issuecomment-2083622569 |
| 35 | +* Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001) |
| 36 | + * Rafael volunteers for the next one |
| 37 | + |
| 38 | + |
| 39 | +* Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999) |
| 40 | + * Richard volunteers to help with the onboarding tasks that are pending. |
| 41 | + * Antoine will prepare another release |
| 42 | +* PGP keys verification [#965](https://github.com/nodejs/Release/issues/965) |
| 43 | + * It will be removed from the agenda |
| 44 | + * Ulises will close the issue as soon as it is ready |
| 45 | +* Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) |
| 46 | + * We are looking for volunteers that can help |
| 47 | +* Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) |
| 48 | + * Seems like there are some PRs that can land in the next 18.x. https://github.com/nodejs/node/pulls?q=is%3Apr+label%3Alts-watch-v18.x+is%3Aclosed |
| 49 | + * We don’t see the need yet to do the release just for this. |
| 50 | + |
| 51 | + |
| 52 | +### nodejs/citgm |
| 53 | + |
| 54 | +* Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060) |
| 55 | + * Discussion around potential ways to improve the current situation |
| 56 | + |
| 57 | + |
| 58 | +## Q&A, Other |
| 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