Release Process

update translations (ping wumpus, Diapolo or tcatm on IRC)
see https://github.com/dashpay/dash/blob/master/doc/translation_process.md#syncing-with-transifex

###update (commit) version in sources

contrib/verifysfbinaries/verify.sh
doc/README*
share/setup.nsi
src/clientversion.h (change CLIENT_VERSION_IS_RELEASE to true)

###tag version in git

git tag -s v(new version, e.g. 0.8.0)

###write release notes. git shortlog helps a lot, for example:

git shortlog --no-merges v(current version, e.g. 0.7.2)..v(new version, e.g. 0.8.0)

###update gitian

In order to take advantage of the new caching features in gitian, be sure to update to a recent version (e9741525c or higher is recommended)

###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=(new version, e.g. 0.8.0)
pushd ./dash
git checkout v${VERSION}
popd
pushd ./gitian-builder
    mkdir -p inputs; cd inputs/

###fetch and build inputs: (first time, or when dependency versions change)

mkdir -p inputs

https://developer.apple.com/downloads/download.action?path=Developer_Tools/xcode_4.6.3/xcode4630916281a.dmg

Using a Mac, create a tarball for the 10.7 SDK and copy it to the inputs directory:

tar -C /Volumes/Xcode/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ -czf MacOSX10.7.sdk.tar.gz MacOSX10.7.sdk

###Optional: Seed the Gitian sources cache

By default, gitian will fetch source files as needed. For offline builds, they can be fetched ahead of time:

make -C ../dash/depends download SOURCES_PATH=`pwd`/cache/common

Only missing files will be fetched, so this is safe to re-run for each build.

###Build Dash Core for Linux, Windows, and OS X:

./bin/gbuild --commit dash=v${VERSION} ../dash/contrib/gitian-descriptors/gitian-linux.yml
./bin/gsign --signer $SIGNER --release ${VERSION}-linux --destination ../gitian.sigs/ ../dash/contrib/gitian-descriptors/gitian-linux.yml
mv build/out/dash-*.tar.gz build/out/src/dash-*.tar.gz ../
./bin/gbuild --commit dash=v${VERSION} ../dash/contrib/gitian-descriptors/gitian-win.yml
./bin/gsign --signer $SIGNER --release ${VERSION}-win --destination ../gitian.sigs/ ../dash/contrib/gitian-descriptors/gitian-win.yml
mv build/out/dash-*.zip build/out/dash-*.exe ../
./bin/gbuild --commit bitcoin=v${VERSION} ../dash/contrib/gitian-descriptors/gitian-osx.yml
./bin/gsign --signer $SIGNER --release ${VERSION}-osx-unsigned --destination ../gitian.sigs/ ../dash/contrib/gitian-descriptors/gitian-osx.yml
mv build/out/dash-*-unsigned.tar.gz inputs/dash-osx-unsigned.tar.gz
mv build/out/dash-*.tar.gz build/out/dash-*.dmg ../
popd

Build output expected:

source tarball (dash-${VERSION}.tar.gz)
linux 32-bit and 64-bit binaries dist tarballs (dash-${VERSION}-linux[32|64].tar.gz)
windows 32-bit and 64-bit installers and dist zips (dash-${VERSION}-win[32|64]-setup.exe, dash-${VERSION}-win[32|64].zip)
OSX unsigned installer (dash-${VERSION}-osx-unsigned.dmg)
Gitian signatures (in gitian.sigs/${VERSION}-<linux|win|osx-unsigned>/(your gitian key)/

###Next steps: pushd gitian.sigs git add ${VERSION}-linux/${SIGNER} git add ${VERSION}-win/${SIGNER} git add ${VERSION}-osx/${SIGNER} git commit -a git push # Assuming you can push to the gitian.sigs tree popd

Commit your signature to gitian.sigs:

pushd gitian.sigs
git add ${VERSION}-linux/${SIGNER}
git add ${VERSION}-win/${SIGNER}
git add ${VERSION}-osx-unsigned/${SIGNER}
git commit -a
git push  # Assuming you can push to the gitian.sigs tree
popd

Wait for OSX detached signature: Once the OSX build has 3 matching signatures, Evan(?) TODO will sign it with the apple App-Store key. He will then upload a detached signature to be combined with the unsigned app to create a signed binary.

Create the signed OSX binary:

pushd ./gitian-builder
# Fetch the signature as instructed by Evan
cp signature.tar.gz inputs/
./bin/gbuild -i ../dash/contrib/gitian-descriptors/gitian-osx-signer.yml
./bin/gsign --signer $SIGNER --release ${VERSION}-osx-signed --destination ../gitian.sigs/ ../dash/contrib/gitian-descriptors/gitian-osx-signer.yml
mv build/out/dash-osx-signed.dmg ../dash-${VERSION}-osx.dmg
popd

Commit your signature for the signed OSX binary:

pushd gitian.sigs
git add ${VERSION}-osx-signed/${SIGNER}
git commit -a
git push  # Assuming you can push to the gitian.sigs tree
popd

After 3 or more people have gitian-built and their results match:

Perform code-signing.
- Code-sign Windows -setup.exe (in a Windows virtual machine using signtool)
Note: only Evan has the code-signing keys currently.
Create SHA256SUMS.asc for the builds, and GPG-sign it:

sha256sum * > SHA256SUMS
gpg --digest-algo sha256 --clearsign SHA256SUMS # outputs SHA256SUMS.asc
rm SHA256SUMS

(the digest algorithm is forced to sha256 to avoid confusion of the Hash: header that GPG adds with the SHA256 used for the files)

Upload zips and installers, as well as SHA256SUMS.asc from last step, to the bitcoin.org server
Update dashpay.io version
- Make a pull request to add a file named YYYY-MM-DD-vX.Y.Z.md with the release notes to https://github.com/dashpay/dashpay.io/tree/master/_releases TODO (Example for 0.9.2.1). TODO
- After the pull request is merged, the website will automatically show the newest version, as well as update the OS download links. Ping Saivann in case anything goes wrong
Announce the release:
- Release sticky on dashtalk: https://dashtalk.org/index.php?board=1.0 TODO
- Dash-development mailing list
- Update title of #dashpay on Freenode IRC
- Optionally reddit /r/Dashpay, ... but this will usually sort out itself
Notify Flare (?) TODO so that he can start building [https://launchpad.net/~dashpay/+archive/ubuntu/dash](the PPAs) TODO
Add release notes for the new version to the directory doc/release-notes in git master
Celebrate

6.2 KiB Raw Blame History

Release Process

After 3 or more people have gitian-built and their results match:

6.2 KiB

Raw Blame History