@nodejs/releasers health #1036
Comments
FWIW this discrepancy is because #1024 hasn't landed yet (but the teams have been updated). More specifically, I was keeping that open to track the offboarding checklist in #1024 (comment). Edit: landed now so the lists are in sync. |
|
SGTM - this is somewhat worrisome. We should try to recruit more releasers (says somebody who has never done a Node.js release after being on the TSC for many years :/). |
|
fwiw I'm still happy to be a releaser, if "not being a collaborator" stops being a barrier. |
|
Pinging the ones that are subject to be moved to emeritus: If any of you would like to remain on the active list, please let me know! I'll proceed with this right after the next releasers meeting. |
I've been a bit busy lately, but I had previously volunteered (#926) and that did not really move forward. |
@RafaelGSS Please leave me on the active list for now as I still plan to contribute whenever possible |
|
@RafaelGSS I would like to continue being a releaser. |
|
Looks like we won't have a Releasers meeting anytime soon. I'll proceed with off-boarding at the end of the week.
|
This comment was marked as resolved.
This comment was marked as resolved.
Sorry I meant Node.js collaborator |
* doc: move releasers to emeritus Refs: #1036 * fixup! doc: move releasers to emeritus
I volunteer! We already talked with @RafaelGSS and I've started attending meetings to get an idea of how things work, and I'll try to step up the contributions to hopefully get a Collaborator status soon |
Refs: nodejs/Release#1042 PR-URL: #55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1040 PR-URL: #55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1041 PR-URL: #55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1042 PR-URL: #55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1040 PR-URL: #55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1041 PR-URL: #55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1042 PR-URL: nodejs#55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1040 PR-URL: nodejs#55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/Release#1041 PR-URL: nodejs#55399 Refs: nodejs/Release#1036 Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Marco Ippolito <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Ulises Gascón <[email protected]> Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Hi folks,
During the latest Node.js Release WG meeting we discussed the project health and the importance of leaving only active members with permissions for the threats evaluated by nodejs/TSC#1618.
Currently, we have a list of 11 releasers (in the README, and 10 with permissions https://github.com/orgs/nodejs/teams/releasers) but just a few of them are making releases this year. The idea is to finalize this task with a real active nodejs releasers list and seek new releasers if needed (possibly yes).
This is the list of 2024 releases: https://github.com/RafaelGSS/nodejs-stats/blob/main/releases/2024-releases.csv.
Releasers:
cc: @nodejs/releasers
The text was updated successfully, but these errors were encountered: