Definition
The Bitcoin Core release process is the documented sequence of steps that turns the project's source tree into versioned, verifiable binaries. It is conservative by design, because the software validates consensus rules and runs on tens of thousands of independent nodes. The process is recorded in the repository so that any contributor can follow or audit it, rather than trusting a single packager.
Branching and release candidates
For a major version, maintainers create a dedicated release branch and update version variables in the build configuration. Before tagging, they refresh release notes, manual pages, and supported-BIP documentation. One or more release candidates (rc1, rc2, and so on) are published first, giving node operators and exchanges time to test against real workloads. Only after candidates prove stable is a final tag created, using maintainer tooling that performs last-minute consistency checks and produces a signed git tag.
Building and signing
Official binaries are produced with deterministic tooling so that independent builders can recreate identical outputs. Multiple builders attest to matching results, and platform code-signing is applied once enough matching signatures exist. The result is a release that users can verify rather than simply trust.
The deterministic step relies on reproducible builds, and merge decisions feeding each release follow the project's lazy consensus model.
In Simple Terms
The Bitcoin Core release process is the documented sequence of steps that turns the project’s source tree into versioned, verifiable binaries. It is conservative by…