Difference between revisions of "Release process"

From Bitcoin Wiki
Jump to: navigation, search
(Bitcoin Core Open Source Release Process: Clarify that the BitcoinTalk forum post is a sticky.)
(External Links: Add entry for Bitcoin Core Release Process on Github.)
 
Line 26: Line 26:
 
==External Links==
 
==External Links==
  
* [https://github.com/bitcoin/bitcoin Bitcoin.org client source] project on Github
+
* [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
 
* [https://github.com/bitcoin/gitian.sigs Gitain.sigs] Trusted build process signatures on Github
 
* [http://bitcoin.org Bitcoin.org] website with releases
 
* [http://bitcoin.org Bitcoin.org] website with releases

Latest 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

See Also