Difference between revisions of "Release process"

From Bitcoin Wiki
Jump to: navigation, search
(Verifying The Download: Add mention of script to verify the binaries.)
(Bitcoin Open Source Release Process: Reference this is for Bitcoin Core specifically.)
Line 1: Line 1:
== Bitcoin Open Source Release Process ==
+
== Bitcoin Core Open Source Release Process ==
  
Releases to the [[Original_Bitcoin_client|Bitcoin.org client]] project are built and released using this process:
+
Releases to the [[Original_Bitcoin_client|Bitcoin Core]] client and project are built and released using this process:
  
 
* Labeled in github
 
* Labeled in github

Revision as of 10:00, 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 sourceforge
  • Blog post on Bitcoin.org
  • Forum post 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