sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-27 13:03:17 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
9cc91523db
dash/doc/release-process.md

173 lines
7.2 KiB
Markdown
Raw Normal View History

Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
Release Process
====================
* update translations (ping wumpus, Diapolo or tcatm on IRC)
* see https://github.com/bitcoin/bitcoin/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
Change release-process.md to sign release tags
2013-12-06 01:26:40 +01:00
git tag -s v(new version, e.g. 0.8.0)
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
###write release notes. git shortlog helps a lot, for example:
Made more generic by removing specific version references Tweaked a little bit to provide examples. Squashed commits into 1, while hoping not to break anything
2013-05-25 22:29:28 +02:00
git shortlog --no-merges v(current version, e.g. 0.7.2)..v(new version, e.g. 0.8.0)
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
* * *
gitian: quick docs update
2014-08-13 01:24:05 +02:00
###update gitian
Ideal release process for Windows detached signing This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]
2015-06-26 14:48:41 +02:00
In order to take advantage of the new caching features in gitian, be sure to update to a recent version (`e9741525c` or later is recommended)
gitian: quick docs update
2014-08-13 01:24:05 +02:00
Fix formatting in release-process.md
2014-07-02 10:32:02 +02:00
###perform gitian builds
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
From a directory containing the bitcoin source, gitian-builder and gitian.sigs
export SIGNER=(your gitian key, ie bluematt, sipa, etc)
Made more generic by removing specific version references Tweaked a little bit to provide examples. Squashed commits into 1, while hoping not to break anything
2013-05-25 22:29:28 +02:00
export VERSION=(new version, e.g. 0.8.0)
Fix and improve release-process.md This commit adds a step, which is to git checkout the version to be built. This ensures that the gitian-descriptors for said version will be the correct ones. In addition, it updates the links for several dependencies, where the previously existing links were dead.
2013-09-24 21:31:52 +02:00
pushd ./bitcoin
git checkout v${VERSION}
popd
Made the build/release process completable verbatim as listed in release-process.md
2013-07-07 18:24:15 +02:00
pushd ./gitian-builder
gitian: Add OSX build descriptors Github-Pull: #4185 Rebased-By: Wladimir J. van der Laan Rebased-From: bb5da27, 2288206, 7fe8fe6, f76db78, ebcf375, fa1ed7c, 397e9b8
2014-05-14 01:23:22 +02:00
Fix formatting in release-process.md
2014-07-02 10:32:02 +02:00
###fetch and build inputs: (first time, or when dependency versions change)
gitian: Add OSX build descriptors Github-Pull: #4185 Rebased-By: Wladimir J. van der Laan Rebased-From: bb5da27, 2288206, 7fe8fe6, f76db78, ebcf375, fa1ed7c, 397e9b8
2014-05-14 01:23:22 +02:00
docs: release process fixups Add instructions for manually fetching sources, as well as some misc. fixes.
2014-12-12 00:53:24 +01:00
mkdir -p inputs
gitian: add a gitian-win-signer descriptor This is exactly like the current OSX signing process. osslsigncode has been patched to detach and re-attach Windows signatures. The changes can be seen here: https://github.com/theuni/osslsigncode/commits/attach-signature There's a pull-request open upstream for the changes: https://sourceforge.net/p/osslsigncode/osslsigncode/merge-requests/3/ This work has been back-ported to the stable 1.7.1 release of osslsigncode, so that a smaller patch can be reviewed.
2015-06-19 00:17:36 +02:00
wget -P inputs https://bitcoincore.org/cfields/osslsigncode-Backports-to-1.7.1.patch
wget -P inputs http://downloads.sourceforge.net/project/osslsigncode/osslsigncode/osslsigncode-1.7.1.tar.gz
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
Clean up release-process.md after OS X gitian changes This is PR #4271, but with the changes to the descriptors, both the names of the files and the names of the intermediate build artifact archives, removed. This also closes #3775 if it goes in, because it covers the changes in that PR.
2014-07-01 18:29:44 +02:00
Register and download the Apple SDK: (see OSX Readme for details)
Bugfix: Correct links for Xcode download
2015-06-05 04:29:41 +02:00
https://developer.apple.com/devcenter/download.action?path=/Developer_Tools/xcode_6.1.1/xcode_6.1.1.dmg
Clean up release-process.md after OS X gitian changes This is PR #4271, but with the changes to the descriptors, both the names of the files and the names of the intermediate build artifact archives, removed. This also closes #3775 if it goes in, because it covers the changes in that PR.
2014-07-01 18:29:44 +02:00
osx: bump build sdk to 10.9
2015-01-20 06:20:44 +01:00
Using a Mac, create a tarball for the 10.9 SDK and copy it to the inputs directory:
Clean up release-process.md after OS X gitian changes This is PR #4271, but with the changes to the descriptors, both the names of the files and the names of the intermediate build artifact archives, removed. This also closes #3775 if it goes in, because it covers the changes in that PR.
2014-07-01 18:29:44 +02:00
osx: bump build sdk to 10.9
2015-01-20 06:20:44 +01:00
tar -C /Volumes/Xcode/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ -czf MacOSX10.9.sdk.tar.gz MacOSX10.9.sdk
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
docs: release process fixups Add instructions for manually fetching sources, as well as some misc. fixes.
2014-12-12 00:53:24 +01:00
###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 ../bitcoin/depends download SOURCES_PATH=`pwd`/cache/common
Only missing files will be fetched, so this is safe to re-run for each build.
###Build Bitcoin Core for Linux, Windows, and OS X:
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
Make gitian builds consistent across platforms Change Linux deps to use a zip archive rather than a gzipped tarball to match win32 Rename Linux descriptor to gitian-linux.yml to match win32
2014-01-15 21:51:37 +01:00
./bin/gbuild --commit bitcoin=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-linux.yml
Clean up release-process.md after OS X gitian changes This is PR #4271, but with the changes to the descriptors, both the names of the files and the names of the intermediate build artifact archives, removed. This also closes #3775 if it goes in, because it covers the changes in that PR.
2014-07-01 18:29:44 +02:00
./bin/gsign --signer $SIGNER --release ${VERSION}-linux --destination ../gitian.sigs/ ../bitcoin/contrib/gitian-descriptors/gitian-linux.yml
release: update docs to reflect new layout - Split linux32/linux64 releases - Split win32/win64 zips - Post-processing should no longer be required. The deterministic outputs are ready for consumption.
2014-11-26 00:37:34 +01:00
mv build/out/bitcoin-*.tar.gz build/out/src/bitcoin-*.tar.gz ../
gitian: Windows 64 bit support - Build a 64 bit version of all dependencies - Show 32/64 bit version in "About..." for x86 - Export 64-bit .exes and installer from gitian build
2014-01-20 13:38:50 +01:00
./bin/gbuild --commit bitcoin=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-win.yml
Ideal release process for Windows detached signing This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]
2015-06-26 14:48:41 +02:00
./bin/gsign --signer $SIGNER --release ${VERSION}-win-unsigned --destination ../gitian.sigs/ ../bitcoin/contrib/gitian-descriptors/gitian-win.yml
mv build/out/bitcoin-*-win-unsigned.tar.gz inputs/bitcoin-win-unsigned.tar.gz
mv build/out/bitcoin-*.zip build/out/bitcoin-*.exe ../
release: update docs to reflect new layout - Split linux32/linux64 releases - Split win32/win64 zips - Post-processing should no longer be required. The deterministic outputs are ready for consumption.
2014-11-26 00:37:34 +01:00
./bin/gbuild --commit bitcoin=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-osx.yml
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
./bin/gsign --signer $SIGNER --release ${VERSION}-osx-unsigned --destination ../gitian.sigs/ ../bitcoin/contrib/gitian-descriptors/gitian-osx.yml
Ideal release process for Windows detached signing This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]
2015-06-26 14:48:41 +02:00
mv build/out/bitcoin-*-osx-unsigned.tar.gz inputs/bitcoin-osx-unsigned.tar.gz
release: update docs to reflect new layout - Split linux32/linux64 releases - Split win32/win64 zips - Post-processing should no longer be required. The deterministic outputs are ready for consumption.
2014-11-26 00:37:34 +01:00
mv build/out/bitcoin-*.tar.gz build/out/bitcoin-*.dmg ../
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
popd
Build output expected:
release: update docs to reflect new layout - Split linux32/linux64 releases - Split win32/win64 zips - Post-processing should no longer be required. The deterministic outputs are ready for consumption.
2014-11-26 00:37:34 +01:00
1. source tarball (bitcoin-${VERSION}.tar.gz)
Ideal release process for Windows detached signing This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]
2015-06-26 14:48:41 +02:00
2. linux 32-bit and 64-bit dist tarballs (bitcoin-${VERSION}-linux[32|64].tar.gz)
3. windows 32-bit and 64-bit unsigned installers and dist zips (bitcoin-${VERSION}-win[32|64]-setup-unsigned.exe, bitcoin-${VERSION}-win[32|64].zip)
4. OSX unsigned installer and dist tarball (bitcoin-${VERSION}-osx-unsigned.dmg, bitcoin-${VERSION}-osx64.tar.gz)
5. Gitian signatures (in gitian.sigs/${VERSION}-<linux|{win,osx}-unsigned>/(your gitian key)/
doc: Add instructions for consistent Mac OS X build names
2014-09-27 20:47:12 +02:00
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
###Next steps:
Commit your signature to gitian.sigs:
pushd gitian.sigs
Clean up release-process.md after OS X gitian changes This is PR #4271, but with the changes to the descriptors, both the names of the files and the names of the intermediate build artifact archives, removed. This also closes #3775 if it goes in, because it covers the changes in that PR.
2014-07-01 18:29:44 +02:00
git add ${VERSION}-linux/${SIGNER}
Ideal release process for Windows detached signing This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]
2015-06-26 14:48:41 +02:00
git add ${VERSION}-win-unsigned/${SIGNER}
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
git add ${VERSION}-osx-unsigned/${SIGNER}
git commit -a
git push # Assuming you can push to the gitian.sigs tree
popd
gitian: add a gitian-win-signer descriptor This is exactly like the current OSX signing process. osslsigncode has been patched to detach and re-attach Windows signatures. The changes can be seen here: https://github.com/theuni/osslsigncode/commits/attach-signature There's a pull-request open upstream for the changes: https://sourceforge.net/p/osslsigncode/osslsigncode/merge-requests/3/ This work has been back-ported to the stable 1.7.1 release of osslsigncode, so that a smaller patch can be reviewed.
2015-06-19 00:17:36 +02:00
Wait for Windows/OSX detached signatures:
Once the Windows/OSX builds each have 3 matching signatures, they will be signed with their respective release keys.
Detached signatures will then be committed to the bitcoin-detached-sigs repository, which can be combined with the unsigned apps to create signed binaries.
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
docs: release process fixups Add instructions for manually fetching sources, as well as some misc. fixes.
2014-12-12 00:53:24 +01:00
Create the signed OSX binary:
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
pushd ./gitian-builder
gitian: Use the new bitcoin-detached-sigs git repo for OSX signatures Rather than fetching a signature.tar.gz from somewhere on the net, instruct Gitian to use a signature from a tag in the bitcoin-detached-sigs repository which corresponds to the tag of the release being built. This changes detached-sig-apply.sh to take a dirname rather than a tarball as an argument, though detached-sig-create.sh still outputs a tarball for convenience.
2015-06-10 19:59:41 +02:00
./bin/gbuild -i --commit signature=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-osx-signer.yml
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
./bin/gsign --signer $SIGNER --release ${VERSION}-osx-signed --destination ../gitian.sigs/ ../bitcoin/contrib/gitian-descriptors/gitian-osx-signer.yml
dmg: fix deterministic dmg creation and docs
2014-12-30 08:36:58 +01:00
mv build/out/bitcoin-osx-signed.dmg ../bitcoin-${VERSION}-osx.dmg
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
popd
gitian: add a gitian-win-signer descriptor This is exactly like the current OSX signing process. osslsigncode has been patched to detach and re-attach Windows signatures. The changes can be seen here: https://github.com/theuni/osslsigncode/commits/attach-signature There's a pull-request open upstream for the changes: https://sourceforge.net/p/osslsigncode/osslsigncode/merge-requests/3/ This work has been back-ported to the stable 1.7.1 release of osslsigncode, so that a smaller patch can be reviewed.
2015-06-19 00:17:36 +02:00
Create the signed Windows binaries:
pushd ./gitian-builder
./bin/gbuild -i --commit signature=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-win-signer.yml
./bin/gsign --signer $SIGNER --release ${VERSION}-win-signed --destination ../gitian.sigs/ ../bitcoin/contrib/gitian-descriptors/gitian-win-signer.yml
Ideal release process for Windows detached signing This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]
2015-06-26 14:48:41 +02:00
mv build/out/bitcoin-*win64-setup.exe ../bitcoin-${VERSION}-win64-setup.exe
mv build/out/bitcoin-*win32-setup.exe ../bitcoin-${VERSION}-win32-setup.exe
gitian: add a gitian-win-signer descriptor This is exactly like the current OSX signing process. osslsigncode has been patched to detach and re-attach Windows signatures. The changes can be seen here: https://github.com/theuni/osslsigncode/commits/attach-signature There's a pull-request open upstream for the changes: https://sourceforge.net/p/osslsigncode/osslsigncode/merge-requests/3/ This work has been back-ported to the stable 1.7.1 release of osslsigncode, so that a smaller patch can be reviewed.
2015-06-19 00:17:36 +02:00
popd
Commit your signature for the signed OSX/Windows binaries:
docs: add/update docs for osx dmg signing
2014-11-26 01:23:18 +01:00
pushd gitian.sigs
git add ${VERSION}-osx-signed/${SIGNER}
gitian: add a gitian-win-signer descriptor This is exactly like the current OSX signing process. osslsigncode has been patched to detach and re-attach Windows signatures. The changes can be seen here: https://github.com/theuni/osslsigncode/commits/attach-signature There's a pull-request open upstream for the changes: https://sourceforge.net/p/osslsigncode/osslsigncode/merge-requests/3/ This work has been back-ported to the stable 1.7.1 release of osslsigncode, so that a smaller patch can be reviewed.
2015-06-19 00:17:36 +02:00
git add ${VERSION}-win-signed/${SIGNER}
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
git commit -a
git push # Assuming you can push to the gitian.sigs tree
popd
-------------------------------------------------------------------------
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
### After 3 or more people have gitian-built and their results match:
Docs Markdown Cleanup
2013-05-20 06:30:00 +02:00
doc: Update SHA256SUMS.asc step in release-process.md - The Hash: header is prepended by gpg, and states the hashing used by gpg, not what is used to hash the files - Add more detailed steps
2014-09-27 15:58:47 +02:00
- Create `SHA256SUMS.asc` for the builds, and GPG-sign it:
```bash
sha256sum * > SHA256SUMS
doc: update gpg command line for SHA256SUMS.asc in release process
2014-09-29 16:58:30 +02:00
gpg --digest-algo sha256 --clearsign SHA256SUMS # outputs SHA256SUMS.asc
doc: Update SHA256SUMS.asc step in release-process.md - The Hash: header is prepended by gpg, and states the hashing used by gpg, not what is used to hash the files - Add more detailed steps
2014-09-27 15:58:47 +02:00
rm SHA256SUMS
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
```
doc: update gpg command line for SHA256SUMS.asc in release process
2014-09-29 16:58:30 +02:00
(the digest algorithm is forced to sha256 to avoid confusion of the `Hash:` header that GPG adds with the SHA256 used for the files)
doc: Add note-to-self about SHA256SUMS to release-process.md
2015-02-16 10:37:13 +01:00
Note: check that SHA256SUMS itself doesn't end up in SHA256SUMS, which is a spurious/nonsensical entry.
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
- Upload zips and installers, as well as `SHA256SUMS.asc` from last step, to the bitcoin.org server
Docs: Use new Bitcoin.org download URLs
2015-04-03 07:51:31 +02:00
into `/var/www/bin/bitcoin-core-${VERSION}`
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
- Update bitcoin.org version
Docs: Use new Bitcoin.org download URLs
2015-04-03 07:51:31 +02:00
- First, check to see if the Bitcoin.org maintainers have prepared a
release: https://github.com/bitcoin/bitcoin.org/labels/Releases
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
Docs: Use new Bitcoin.org download URLs
2015-04-03 07:51:31 +02:00
- If they have, it will have previously failed their Travis CI
checks because the final release files weren't uploaded.
Trigger a Travis CI rebuild---if it passes, merge.
- If they have not prepared a release, follow the Bitcoin.org release
instructions: https://github.com/bitcoin/bitcoin.org#release-notes
- After the pull request is merged, the website will automatically show the newest version within 15 minutes, as well
as update the OS download links. Ping @saivann/@harding (saivann/harding on Freenode) in case anything goes wrong
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
- Announce the release:
Release process: add section about announcing new release
2013-12-10 09:57:30 +01:00
- Release sticky on bitcointalk: https://bitcointalk.org/index.php?board=1.0
- Bitcoin-development mailing list
doc: Modernize steps to be followed after release Remove old references to sourceforge, add what actually should be done and provide some more details.
2014-08-04 09:47:59 +02:00
- Update title of #bitcoin on Freenode IRC
- Optionally reddit /r/Bitcoin, ... but this will usually sort out itself
- Notify BlueMatt so that he can start building [https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin](the PPAs)
- Add release notes for the new version to the directory `doc/release-notes` in git master
Release process: add section about announcing new release
2013-12-10 09:57:30 +01:00
Non-grammatical language improvements
2015-04-28 16:47:17 +02:00
- Celebrate
Reference in New Issue Copy Permalink