Repository navigation
Two new release team members #924
Description
Ruben Bridgewater ruben@bridgewater.de A48C2BEE680E841632CD4E44F07496B3EB3C1762
Beth Griggs bethany.griggs@uk.ibm.com 4ED778F539E3634C779C87C6D7062848A1AB005C
Ruben Bridgewater ruben@bridgewater.de A48C2BEE680E841632CD4E44F07496B3EB3C1762
Beth Griggs bethany.griggs@uk.ibm.com 4ED778F539E3634C779C87C6D7062848A1AB005C
Activity
SimenB commentedon Nov 21, 2018
Mind updating https://github.com/nodejs/docker-node/blob/master/keys/node.keys?
keys: add new keys and remove old keys
MylesBorins commentedon Nov 21, 2018
@SimenB done
SimenB commentedon Nov 21, 2018
@MylesBorins is there some document that mandates an issue in this repo for new releasers? If so, maybe update it to just send a PR instead?
chorrell commentedon Nov 21, 2018
For reference (the changes to the release keys)
SimenB commentedon Nov 21, 2018
Best would be if this was in some document on nodejs.org that we could pull down in our
update.shscriptPeterDaveHello commentedon Nov 22, 2018
@SimenB https://github.com/nodejs/node#release-team
MylesBorins commentedon Nov 22, 2018
@SimenB --> https://github.com/nodejs/Release/blob/master/GOVERNANCE.md#adding-new-releasers
We are updating the text right now and I suggested changing it to be a PR
nodejs/Release#393