Nominating new Release team members

[Fishrock123]

You do not have to be a TSC / CTC member to do releases.

Nominating two so far (also since they've volunteered their time)

• @evanlucas (Release a v5.2.1? #4316 (comment))
• @thealphanerd (Release a v5.2.1? #4316 (comment))

cc @nodejs/ctc

[jasnell]

+1 to both!

[rvagg]

yar, +1 on both, particularly since @thealphanerd has been doing a lot of the heavy lifting with staging branches recently

[cjihrig]

+1 to both. I think we should cap it at those two for the time being though.

[bnoordhuis]

One more +1.

[Fishrock123]

I suppose the thing to do it to bring it up on the next TSC meeting then.

[jasnell]

@Fishrock123 ... I'm not sure that's necessary. Seems like everyone is in agreement :-)

[rvagg]

I wouldn't mind a CTC quorum on this, releases are a big deal and we should treat it as such cause you get access to put binaries on the server for redistribution so the CTC is effectively delegating its trust to these individuals. Enough +1's in here would probably be sufficient but I'd prefer a meeting so we have a clearer chain of evidence.

[jasnell]

OK. Works for me

[Fishrock123]

@thealphanerd / @evanlucas note: there's no solid process for this, but generally, we'll try to get you to do a patch or minor release while we are around to help. The actual release process is something you can only really learn to do by actually doing it. :)

[evanlucas]

Works for me!

[MylesBorins]

ditto. Perhaps I can shadow @jasnell on next weeks LTS release

[Fishrock123]

@evanlucas & @thealphanerd could you make sure to have GPG keys setup as per https://github.com/nodejs/node/blob/master/doc/releases.md#3-a-publicly-listed-gpg-key?

Also having them on keybase.io is nice (let me know if you need an invite).