Release process: Difference between revisions
Jump to navigation
Jump to search
(Add reference to Trusted Build Process and create External links section.) |
m (→Bitcoin Open Source Release Process: Fix list.) |
||
| Line 6: | Line 6: | ||
* Binaries are created for the platforms affected (usually all, Windows, Mac and Linux). | * 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. | * 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. | * Files used to build are checksummed and submitted to the Gitian.sigs project on github. | ||
* Uploaded to sourceforge | * Uploaded to sourceforge | ||
* Blog post on Bitcoin.org | * Blog post on Bitcoin.org | ||
Revision as of 09:55, 22 March 2012
Bitcoin Open Source Release Process
Releases to the Bitcoin.org client 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 sourceforge
- Blog post on Bitcoin.org
- Forum post on BitcoinTalk.org
Verifying The Download
To verify the checksums, 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
External Links
- Bitcoin.org client source project on Github
- Gitain.sigs Trusted build process signatures on Github
- Bitcoin.org website with releases