Repository navigation
Proposal: Authorise @Fishrock123 to create releases #1225
Description
@iojs/tc (and anyone else interested in commenting of course)
This is separate the question of Jeremiah on the TC. I actually intended to do this before he was even nominated to the TC by @mikeal simply because it'd be nice to have a broader group of releasers and neat to have someone not on the TC able to do this.
Currently there's myself and @chrisdickinson who are authorized to make releases. This authorization is both organisational (should have sign-off from the TC) and technical (needs GPG key on the README and ssh access to the website for the "dist" user).
We need more people able to make releases so we continue our cadence and not create bottlenecks or have a low bus-factor.
See https://github.com/iojs/io.js/blob/v1.x/doc/releases.md for how the release process works.
Activity
chrisdickinson commentedon Mar 21, 2015
I am +1 on this.
benjamingr commentedon Mar 21, 2015
Sure, sounds good :)
bnoordhuis commentedon Mar 21, 2015
No disagreement from me.
trevnorris commentedon Mar 23, 2015
cool
piscisaureus commentedon Mar 25, 2015
Since there is no tc meeting this week: +1 from me
Fishrock123 commentedon Apr 1, 2015
fwiw I'm willing for this. :)
bnoordhuis commentedon Apr 1, 2015
Unanimously +1'd in today's TC meeting. I'll close the issue but feel free to reopen if it needs to stay open.
rvagg commentedon Apr 1, 2015
@Fishrock123 can you read https://github.com/iojs/io.js/blob/v1.x/doc/releases.md and then do the following:
Fishrock123 commentedon Apr 2, 2015
Sure, I'll get this sorted out tomorrow.
Fishrock123 commentedon Apr 2, 2015
I still need to sort out the SSH thing.
Turns out I haven't used any of the github SSH keys in quite some time; I've been using github's personal access tokens through
credential.helper=osxkeychain.Fishrock123 commentedon Apr 2, 2015
Does it need to be accessible at https://github.com/Fishrock123.keys?
Fishrock123 commentedon Apr 2, 2015
Also, the thing I upload to the sks keyserver for the gpg key should be this, right?
bnoordhuis commentedon Apr 2, 2015
Yes, it should be your public key.
rvagg commentedon Apr 3, 2015
@Fishrock123 re ssh key, just get me your pubkey somehow, if you don't want it on github then perhaps email it to me and sign it with your gpg key that's in the pool, or something
Fishrock123 commentedon Apr 4, 2015
@rvagg it's the last (bottom) one on github now, ending in
fImqwZn6NBrvagg commentedon Apr 4, 2015
done, you should be able to
tools/release.shwhen your keys is on the README and it should look something like this:Import GPG key for Fishrock123