Add release artifacts documentation page#1221
Add release artifacts documentation page#1221PauloAAlmeida wants to merge 3 commits intobitcoin-core:masterfrom
Conversation
| - **Standard Binaries** (`.tar.gz`, `.zip`, `-setup.exe`): Production-ready, signed binaries for general use. | ||
| - **`-debug`**: Includes symbols for backtrace generation. Larger file size and reduced performance. | ||
| - **`-unsigned`**: Raw Guix build outputs. Used to audit reproducibility against signed releases. | ||
| - **`-codesigning`**: Intermediate artifacts for macOS/Windows signing ceremonies. Not for end-users. |
There was a problem hiding this comment.
Actually these artefacts are all signed via the hashes SHA256SUMS file.
Perhaps update in general, and on L25 which also seems to imply only release files are hashed and signed?
There was a problem hiding this comment.
Good catch. Removed "signed" from the standard binaries description and updated SHA256SUMS to clarify it covers all artifacts.
|
@willcl-ark I've addressed your review feedback. The CI failures look unrelated to this change. Ready for another look when you have a chance. |
| - **Standard Binaries** (`.tar.gz`, `.zip`, `-setup.exe`): Production-ready binaries for general use. | ||
| - **`-debug`**: Includes symbols for backtrace generation. Larger file size and reduced performance. |
There was a problem hiding this comment.
Sorry, but I still don't think this is exactly correct.
In the guix builds we produce a single set of bins, using -O2 -g, then post-process them using split-debug.sh. This splits off the symbols into a standalone dbg file. The bins are then stripped, and two archives are created, one with the binaries, and one with the debug symbols.
I don't think it's accurate ∴ to say that the debug bins have "reduced performance", as they're the same bins; the debug archive only contains the symbols IIUC.
cc @fanquake
There was a problem hiding this comment.
Thanks for the clarification. Updated the -debug description.
There was a problem hiding this comment.
@fanquake would you please check if this is accurate? Let me know if you need any adjustments.
There was a problem hiding this comment.
@willcl-ark please let me know if you need any adjustments. Thank you for your review.
|
triggering ci |
Thanks. CI failures appear to be unrelated to this PR. Both failing jobs hit the same pre-existing issue. |
4 participants
Add a page explaining the different file types distributed on the Bitcoin Core download page and in release torrents.
Closes #1220