This was originally directed to Glv, in response to his pull request for a gitian build process for Peerunity (https://github.com/Peerunity/Peerunity/pull/48) but Glv suggested that I post my questions here so that others may benefit from the discussion.
I don’t consider myself to be extremely proficient with Git and even less so with Gitian. My questions deal specifically with the first part of the release process (https://github.com/Peerunity/Peerunity/blob/master/doc/release-process.txt) …
* update translations (ping tcatm on IRC for now) * update (commit) version in sources bitcoin-qt.pro src/version.h share/setup.nsi doc/README* * tag version in git git tag -a v0.5.1 * write release notes. git shortlog helps a lot: git shortlog --no-merges v0.5.0.. * perform gitian builds * From a directory containing the bitcoin source, gitian-builder and gitian.sigs export SIGNER=(your gitian key, ie bluematt, sipa, etc) export VERSION=0.5.1
What part of the above steps are necessary if all I’m trying to do is test the process?
Does it matter which signer is used and how do you create new signers?