aboutsummaryrefslogtreecommitdiff
path: root/doc/release-process.md
AgeCommit message (Collapse)Author
2019-01-21Delete README_osx.md and move its contents into build-osx.mdMartin Erlandsson
2019-01-15Merge #14433: Add checksum in gitian build scripts for osslWladimir J. van der Laan
03b8596dd665d2f70c917794295911adb8680bcc Add checksum in gitian build scripts for ossl (TheCharlatan) Pull request description: This adds a checksum in the gitian build script to make sure that ossl tool and theuni's patch matches what is expected. Also changes the url to use https. Tree-SHA512: bd25acda1c7d9ca94e710bdfa915d20810101e10b0c68913a00fcb0eada25cdc2d59f7efebc822e07dea7eaab058024e6c53031883ded0ecf9f08212e50a25b3
2019-01-11Merge #13216: [Qt] implements concept for different disk sizes on introJonas Schnelli
9d0e52834 implements different disk sizes for different networks on intro (marcoagner) Pull request description: Fixes https://github.com/bitcoin/bitcoin/issues/13213. Mostly, I layed out the concept to open the PR for refinement and getting feedback if the approach is okay. Changes are expected. Two points: - The values for both new consts `TESTNET_BLOCK_CHAIN_SIZE` and `TESTNET_CHAIN_STATE_SIZE` is certainly not optimal; I just checked the size of my testnet3 related dirs and set them to little bit higher values. Which values should be used? - Should we do something like this to regtest? Or these "niceties" do not matter when on regtest? Thanks! Tree-SHA512: 8ae87a29fa8356b899e7a823c76cde793d9126b4ee59554d7a2a8edb088fe42a19976b34c06c2fd4a98a727e1e4971dd983f42b6093ea6caa255b45004e22bb4
2019-01-09Add checksum in gitian build scripts for osslTheCharlatan
This adds a checksum in the gitian build script to make sure that ossl tool and theuni's patch matches what is expected. Also changes the url to use https and adds the same instructions to the release docs.
2018-11-24http -> httpsDimitris Apostolou
2018-11-01Update release-process.md to include RC version bumpingAndrew Chow
2018-10-07implements different disk sizes for different networks on intromarcoagner
- Creates m_assumed_blockchain_size and m_assumed_chain_state_size on CChainParams. - Implements access to CChainParams' m_assumed_blockchain_size and m_assumed_chain_state_size on node interface. - Implements m_assumed_blockchain_size and m_assumed_chain_state_size on qt/intro via node interface. - Updates release process document with the new CChainParam's values.
2018-10-04doc: RPC documentationKarel Bílek
2018-07-19doc: Improve command to generate list of authors for release notesMitchell Cash
- Remove dependency on sed (sed was overkill when you can just add plain text to the git log --format command) - Sort resulting list of authors alphabetically (case-insensitive) - Provide an example of how to only generate authors between versions
2018-07-19doc: Update broken links to now point to gitian-build.pyMitchell Cash
2018-07-17contrib: Clone core repo in gitian-buildMarcoFalke
2018-06-04Rename “OS X” to the newer “macOS” conventionGiulio Lombardo
2018-05-30doc: update bitcoin-dot-org links in release-process.mdfanquake
2018-03-06Give hint about gitian not able to downloadkallewoof
Gitian fails to perform downloads right now on my set up. This can be circumvented by first checking out the tag being built and then doing the depends download step before running `gbuild`.
2018-03-06doc: SIGNER can contains space inside now.Ken Lee
SIGNER can contains space inside now. mentioned in https://github.com/bitcoin/bitcoin/pull/12527#issuecomment-370506416
2018-02-06Merge #11909: contrib: Replace developer keys with list of pgp fingerprintsWladimir J. van der Laan
fabb72b contrib: Remove xpired 522739F6 key (MarcoFalke) faeab66 contrib: Replace developer keys with list of pgp fingerprints (MarcoFalke) Pull request description: Having to host a copy of the keys in this repo was a common source of discussion and distraction, caused by problems such as: * Outdated keys. Unclear whether and when to replace by fresh copies. * Unclear when to add a key of a new developer or Gitian builder. The problems are solved by * Having no keys but only the fingerprints * Adding a rule of thumb, when to add a new key <strike>Moving the keys to a different repo solves none of these issues, but since the keys are not bound to releases or git branches of Bitcoin Core, they should live somewhere else. Obviously, all keys are hosted and distributed on key servers, but were added to the repo solely for convenience and redundancy. Moving the mirror of those keys to a different repo makes it less distracting to update them -- let's say -- prior to every major release. I updated our `doc/release-process.md` to reflect the new location. DEPENDS_ON https://github.com/bitcoin-core/gitian.sigs/pull/621 </strike> Tree-SHA512: c00795a07603190e26dc4526f6ce11e492fb048dc7ef54b38f859b77dcde25f58ec4449f5cf3f85a5e9c2dd2743bde53f7ff03c8eccf0d75d51784a6b164e47d
2018-02-02Merge #12317: Document method for reviewers to verify chainTxDataWladimir J. van der Laan
7444149 Document method for reviewers to verify chainTxData (John Newbery) Pull request description: This commit adds the final block hash of the window to getchaintxstats and documents how reviewers can verify changes to chainTxData. Tree-SHA512: d16abb5f47d058e52660f4d495f1e453205b1b83716d7c810ff62a70338db721386c1808ec1fc8468f514e4d80cc58e3c96eeb3184cbbcb1d07830fa5e53f342
2018-02-02Document method for reviewers to verify chainTxDataJohn Newbery
This commit adds the final block hash of the window to getchaintxstats and documents how reviewers can verify changes to chainTxData.
2018-02-02Merge #12283: Fix typosMarcoFalke
1340eda3b7 Fix typos (practicalswift) Pull request description: Fix typos. Tree-SHA512: 533a136831387ef26e9a74ba078437496bee38cc026da73fa9e6f6e7f4d5665eccac24cf3ef05e6d3af1329a1214f5ce71b039ddb8378b074e6d4408b8701f95
2018-01-31doc: Explain how to update chainTxData in release processWladimir J. van der Laan
Adds a short explanation how to update chainTxData to the release process. Mention where to get the data, and link to an example.
2018-01-28Fix typospracticalswift
2017-12-17contrib: Replace developer keys with list of pgp fingerprintsMarcoFalke
2017-08-13Add instructions for multi-processor gitian buildsCharlie Lee
2017-04-06doc: Update release process for simplified version bumpingWladimir J. van der Laan
2017-03-20Merge #9734: Add updating of chainTxData to release processWladimir J. van der Laan
41b8821 Add updating of chainTxData to release process (Pieter Wuille) Tree-SHA512: f7d6e72b19aa83fc4851a9316d6c6a236e0e914d637525cda42c0b15a94543b8072ce67b57d6b12141332a03b64b6c715dff4d61e6e58e0197b22305b35ad65d
2017-03-13Merge #9514: release: Windows signing scriptWladimir J. van der Laan
09fe2d9 release: update docs to show basic codesigning procedure (Cory Fields) f642753 release: create a bundle for the new signing script (Cory Fields) 0068361 release: add win detached sig creator and our cert chain (Cory Fields) Tree-SHA512: 032ad84697c70faaf857b9187f548282722cffca95d658e36413dc048ff02d9183253373254ffcc1158afb71140753f35abfc9fc8781ea5329c04d13c98759c0
2017-02-09Add updating of chainTxData to release processPieter Wuille
2017-01-13Introduce assumevalid setting to skip presumed valid scripts.Gregory Maxwell
This disentangles the script validation skipping from checkpoints. A new option is introduced "assumevalid" which specifies a block whos ancestors we assume all have valid scriptsigs and so we do not check them when they are also burried under the best header by two weeks worth of work. Unlike checkpoints this has no influence on consensus unless you set it to a block with an invalid history. Because of this it can be easily be updated without risk of influencing the network consensus. This results in a massive IBD speedup. This approach was independently recommended by Peter Todd and Luke-Jr since POW based signature skipping (see PR#9180) does not have the verifiable properties of a specific hash and may create bad incentives. The downside is that, like checkpoints, the defaults bitrot and older releases will sync slower. On the plus side users can provide their own value here, and if they set it to something crazy all that will happen is more time will be spend validating signatures. Checkblocks and checklevel are also moved to the hidden debug options: Especially now that checkblocks has a low default there is little need to change these settings, and users frequently misunderstand them as influencing security or IBD speed. By hiding them we offset the space added by this new option.
2017-01-10release: update docs to show basic codesigning procedureCory Fields
2016-11-07[doc] release-process: Mention GitHub release and archived release notesMarcoFalke
2016-11-02IBD check uses minimumchain work instead of checkpoints.Gregory Maxwell
This introduces a 'minimum chain work' chainparam which is intended to be the known amount of work in the chain for the network at the time of software release. If you don't have this much work, you're not yet caught up. This is used instead of the count of blocks test from checkpoints. This criteria is trivial to keep updated as there is no element of subjectivity, trust, or position dependence to it. It is also a more reliable metric of sync status than a block count.
2016-10-04[doc] Rework docsMarcoFalke
* Minor formatting such as adjusting links * Move sections of `doc/multiwallet-qt.md` to the source code and delete the file, as it is outdated * Fix typo in the release notes * Amend release process to mention update of BLOCK_CHAIN_SIZE
2016-09-30Merge #8852: Mention Gitian building script in doc (Laudaa)Wladimir J. van der Laan
203e2dd Mention Gitian building script in doc. (Lauda)
2016-09-30Mention Gitian building script in doc.Lauda
2016-09-25Remove old manpages from contrib/debianfanquake
2016-08-26[trivial][doc] Mention gpg --refresh-keys in release-process.mdfanquake
2016-07-18[doc] gbuild: Set memory explicitly (default is too low)MarcoFalke
2016-06-22Merge #8233: Mention Linux ARM executables in release process and notesWladimir J. van der Laan
06f40ef depends: Mention aarch64 as common cross-compile target (Wladimir J. van der Laan) 05f64c9 doc: Mention Linux ARM builds in release notes (Wladimir J. van der Laan) b7bf037 doc: Mention ARM executables in release process (Wladimir J. van der Laan)
2016-06-21doc: Mention ARM executables in release processWladimir J. van der Laan
Mention ARM executables in the release process documentation (these were introduced in #8188). As well as that Linux tarballs have changed name to contain an architecture tuple, instead of `linux32`/`linux64`. Also mention that `-debug` files should not be uploaded (these were introduced in #8167).
2016-06-20[Doc] Update OS X build notes for 10.11 SDKfanquake
2016-04-29[doc] Update bitcoin-core GitHub linksMarcoFalke
2016-04-25doc: Update release processWladimir J. van der Laan
The actual release process quite diverged from what was written here, also clarify things a bit.
2016-04-15[gitian] Move keys to contrib/gitian-keysMarcoFalke
2016-03-01[doc] Fix markdownMarcoFalke
2016-02-04[doc] Update release-process.mdMarcoFalke
2016-01-26Minor improvements to the release processPaul Rabahy
Instruct people to "git fetch" so that if this is their 2nd+ gitian build they will have a fresh bitcoin repo. Instruct people to add all the known pgp keys to their keyring so that gverify will print more useful info.
2015-10-18Correct spelling mistakes in doc folderMitchell Cash
- OSX —> OS X - XCode —> Xcode - github —> GitHub - homebrew —> Homebrew - gitian —> Gitian - Other miscellaneous obvious spelling fixes and whitespace removal
2015-10-14[doc] Cleanup release-process documentationMichael
2015-09-17Clarifying offline build process using gbuild --url and noting it is notMidnight Magic
done automatically. At some point along the line, fully offline builds were no longer happening when strictly following the release-process.md instructions. We should ensure that users who might want to torify or build offline need to take extra steps to remain offline. Also, corrections to build process: including gverify examples for new builders.
2015-06-30Ideal release process for Windows detached signingMicha
This is an ideal version of what the release process should look like, making it more consistent with the OS X process. Some of the changes described here would need to be made in the descriptors, which is somewhat beyond what I would feel comfortable doing, not really understanding the signature process in depth. [skip ci]