Release process: Difference between revisions
Jump to navigation
Jump to search
→External Links: Add entry for Bitcoin Core Release Process on Github. |
→Verifying The Download: replace incorrect and misleading information with links to proper resources |
||
| Line 14: | Line 14: | ||
==Verifying The Download== | ==Verifying The Download== | ||
See the verification instructions [https://bitcoincore.org/en/download/ on the Bitcoin Core download page]. | |||
Or try the [https://github.com/bitcoin/bitcoin/tree/master/contrib/verifybinaries script in the Bitcoin Core repository]. | |||
==External Links== | ==External Links== | ||
Revision as of 12:06, 9 August 2019
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
See the verification instructions on the Bitcoin Core download page.
Or try the script in the Bitcoin Core repository.
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