Release process

From Bitcoin Wiki
Revision as of 08:40, 22 March 2012 by Sgornick (talk | contribs) (Add an article to document the release process.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Bitcoin Open Source Release Process

Releases to the 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
  • Forum post on

Verifying The Downloads

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