Release process: Difference between revisions
Jump to navigation
Jump to search
m (Fix section title.) |
(→External Links: Add entry for Bitcoin Core Release Process on Github.) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
== Bitcoin Open Source Release Process == | == Bitcoin Core Open Source Release Process == | ||
Releases to the [[Original_Bitcoin_client|Bitcoin | Releases to the [[Original_Bitcoin_client|Bitcoin Core]] client and project are built and released using this process: | ||
* Labeled in github | * Labeled in github | ||
| Line 7: | Line 7: | ||
* Binary file checksum(s) is(are) calculated and a message with those are signed by a core developer. | * Binary file checksum(s) is(are) calculated and a message with those are signed by a core developer. | ||
** sha256 checksum | ** sha256 checksum | ||
* Uploaded to | * Files used to build are checksummed and submitted to the Gitian.sigs project on github. | ||
* Uploaded to distribution (Bitcoin.org/bin, and Launchpad.net for the Ubuntu PPA) | |||
* Blog post on Bitcoin.org | * Blog post on Bitcoin.org | ||
* Forum post on BitcoinTalk.org | * Forum post (sticky) on BitcoinTalk.org | ||
==Verifying The Download== | ==Verifying The Download== | ||
To verify the | To verify the checksum for a binary download, first ensure the checksum file is secure by decrypting the SHA256SUMS.asc file: | ||
$ gpg --decrypt SHA256SUMS.asc | $ gpg --decrypt SHA256SUMS.asc | ||
| Line 20: | Line 21: | ||
Verify that the checksum matches the one in SHA256SUMS.asc | Verify that the checksum matches the one in SHA256SUMS.asc | ||
A [https://github.com/bitcoin/bitcoin/pull/1935 script to verify the binaries] was contributed to the Bitcoin.org project. | |||
==External Links== | |||
* [https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md Bitcoin Core Release Process] on Github | |||
* [https://github.com/bitcoin/bitcoin Bitcoin Core project source] on Github | |||
* [https://github.com/bitcoin/gitian.sigs Gitain.sigs] Trusted build process signatures on Github | |||
* [http://bitcoin.org Bitcoin.org] website with releases | |||
==See Also== | ==See Also== | ||
| Line 26: | Line 36: | ||
* [[Original Bitcoin client]] | * [[Original Bitcoin client]] | ||
* [[:Category:Open_Source|Open source]] | * [[:Category:Open_Source|Open source]] | ||
[[es:Proceso de publicación de versiones]] | |||
[[Category:Developer]] | [[Category:Developer]] | ||
Revision as of 13:30, 27 September 2015
Bitcoin Core Open Source Release Process
Releases to the Bitcoin Core client and project are built and released using this process:
- Labeled in github
- Binaries are created for the platforms affected (usually all, Windows, Mac and Linux).
- Binary file checksum(s) is(are) calculated and a message with those are signed by a core developer.
- sha256 checksum
- Files used to build are checksummed and submitted to the Gitian.sigs project on github.
- Uploaded to distribution (Bitcoin.org/bin, and Launchpad.net for the Ubuntu PPA)
- Blog post on Bitcoin.org
- Forum post (sticky) on BitcoinTalk.org
Verifying The Download
To verify the checksum for a binary download, first ensure the checksum file is secure by decrypting the SHA256SUMS.asc file:
$ gpg --decrypt SHA256SUMS.asc
Then verify the file checksum:
$ openssl dgst -sha256 [binary release archive]
Verify that the checksum matches the one in SHA256SUMS.asc
A script to verify the binaries was contributed to the Bitcoin.org project.
External Links
- Bitcoin Core Release Process on Github
- Bitcoin Core project source on Github
- Gitain.sigs Trusted build process signatures on Github
- Bitcoin.org website with releases