Repository navigation
Jordan Harband onboarding #911
Description
- Be added to the GitHub releasers team in the Node.js org (grants ci-release access)
- Be added to the GitHub security-release team in the Node.js and nodejs-private orgs
- Have a single, high quality SSH key added to the "dist" user on the primary www server (see below for guidelines regarding SSH key quality)
- Open a PR to add their GPG key to the nodejs/node README.md
- Once landed, the key should be cherry-picked to all active release staging branches (i.e. the active
vMM.x-stagingbranches). - Any future updates to the key should also be cherry-picked to all active release staging branches.
- Once landed, the key should be cherry-picked to all active release staging branches (i.e. the active
- Open a PR in nodejs/docker-node to add their GPG key to node.keys
- Open a PR in nodejs/release-keys to add their GPG key via
./cli.sh add $KEY_ID: - Open a PR in nodejs/Release to add themself under the "Releasers team" heading via
ncu-team sync README.md. - Add them to the
#nodejs-release-privateteam on the OpenJS Slack.
cc: @ljharb
Activity
RafaelGSS commentedon Sep 15, 2023
The next step is to schedule a pair release where Jordan will prepare the release and another releaser will sign it. As I said previously, I can't handle/sign any release this month. I can help with the first release of October. @nodejs/releasers feel free to take the lead on this onboarding if any of you can onboard Jordan sooner than me.
ljharb commentedon Dec 4, 2024
Now that I'm a collaborator, I'd love to do this onboarding :-)
ruyadorno commentedon Dec 4, 2024
Yes!! Now that the collaborator status is figured out let's get the onboarding started, we can def use the help in the Releases team 😊
RafaelGSS commentedon Dec 5, 2024
Right, my suggestion is to participate in at least 2 releasers meeting and then start preparing releases (manually).
Landing backports is also a good start