-
-
Notifications
You must be signed in to change notification settings - Fork 602
Jordan Harband onboarding #911
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
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. |
Now that I'm a collaborator, I'd love to do this onboarding :-) |
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 😊 |
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 |
vMM.x-staging
branches)../cli.sh add $KEY_ID
:ncu-team sync README.md
.#nodejs-release-private
team on the OpenJS Slack.cc: @ljharb
The text was updated successfully, but these errors were encountered: