Difference between revisions of "Release process"

From Bitcoin Wiki
Jump to: navigation, search
m (Interwiki link to new Spanish article)
(Verifying The Download: Add mention of script to verify the binaries.)
Line 21: 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==
 
==External Links==

Revision as of 22:22, 15 October 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 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