Growing the group of releasers #48
Description
I think it's high time we add a couple more people who can do Node.js releases.
Contrary to common (I assume from past interactions) belief, you don't need to be on the CTC to be a releaser. (Although we'd probably want you to be a collaborator.)
As such I'd actually prefer to get one or more non-CTC collaborators to be able to do releases.
cc @nodejs/collaborators
Note: doing releases is a bit time consuming, but you won't be required to do them frequently, only encouraged to do them here and there. :)
(It's really up to you most times, create a release proposal issue and run with it.)
In fact, the best way to start if you are interested would be to propose the next v7 (Current) release! (Anyone can do this part actually! See near the bottom.)
To do so, create a v7.3.0-proposal branch (on the main repo) off of v7.x-staging and create a PR with it stating the version you'd like to propose (like v7.3.0) along with the proposed release date (usually Tuesdays or Wednesdays, never weekends).
If you're not a collaborator and would still like to do this part, you can create an issue on nodejs/node with the proposed version, date, and a list of markdown formatted commits made from changelog-maker or branch-diff (by difference between the head of v7.x-staging and the last 7.x release).