Difference between revisions of "Release process"

From Bitcoin Wiki
Jump to: navigation, search
(Add an article to document the release process.)
 
m (Fix section title.)
Line 11: Line 11:
 
* Forum post on BitcoinTalk.org
 
* Forum post on BitcoinTalk.org
  
==Verifying The Downloads==
+
==Verifying The Download==
  
 
To verify the checksums, first ensure the checksum file is secure by decrypting the SHA256SUMS.asc file:
 
To verify the checksums, first ensure the checksum file is secure by decrypting the SHA256SUMS.asc file:

Revision as of 08:41, 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
  • 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

See Also