aboutsummaryrefslogtreecommitdiff
path: root/doc/release-process.md
Commit message (Collapse)AuthorAgeFilesLines
* doc: fix getchaintxstats fields in release-process.mdJon Atack2020-11-011-6/+5
| | | | | | | | | | | | | also: - use the getblockheader (and getblockhash) RPCs instead of getblockchaininfo for updating the nMinimumChainWork and defaultAssumeValid consensus params - use "RPC" consistently - update the example PR from 17002 to 20263 - improve a link with a named anchor tag
* [doc] fix git add argumentMichael Polzer2020-04-031-1/+1
| | | | | | | | | | | | | | | | | | | | | error: unknown switch `a' usage: git add [<options>] [--] <pathspec>... -n, --dry-run dry run -v, --verbose be verbose -i, --interactive interactive picking -p, --patch select hunks interactively -e, --edit edit current diff and apply -f, --force allow adding otherwise ignored files -u, --update update tracked files --renormalize renormalize EOL of tracked files (implies -u) -N, --intent-to-add record only the fact that the path will be added later -A, --all add changes from all tracked and untracked files --ignore-removal ignore paths removed in the working tree (same as --no-all) --refresh don't add, only refresh the index --ignore-errors just skip files which cannot be added because of errors --ignore-missing check if - even missing - files are ignored in dry run --chmod (+|-)x override the executable bit of the listed files
* doc: remove PPA note from release-process.mdfanquake2020-02-121-3/+1
| | | | Also fixes a link to the macdeploy instructions.
* build: Skip i686 build by default in guix and gitianMarcoFalke2020-02-091-1/+0
|
* Merge #17598: doc: Update release process with latest changesfanquake2019-12-121-5/+9
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fab2f351f2311295c9ed893fe883a08a9104144e doc: Update release process with latest changes (MarcoFalke) Pull request description: Mainly adding the reminder to bump the flatpak ACKs for top commit: laanwj: ACK fab2f351f2311295c9ed893fe883a08a9104144e fanquake: ACK fab2f351f2311295c9ed893fe883a08a9104144e Tree-SHA512: fe279a6cdee881e8dd608cb7d09d992c4b668b01b9d0d2dbfaf92f12f3032b8fcb2c256b20fcee861397451add1338f162b6e5fa7b3c21e76c247cc419315284
| * doc: Update release process with latest changesMarcoFalke2019-12-101-5/+9
| |
* | Fixed wget call in gitian-build.pywillyk2019-12-051-1/+1
|/
* build: use osslsigncode 2.0 in gitianfanquake2019-10-211-4/+2
| | | | | | | | | | The original osslsigncode project (https://sourceforge.net/projects/osslsigncode/) has been marked as abandonware, "This is now - and has been for a long while - abandonware. Feel free to create your own forks etc.". However, a fork at https://github.com/mtrojnar/osslsigncode has emerged that has incorporated theuni's patches, updated the tool to work with OpenSSL 1.1 and made other improvements. This commit switches the windows signer descriptor to use this new version of osslsigncode.
* doc: move-only: Steps for "before major release branch-off"MarcoFalke2019-10-021-10/+10
| | | | | | Can be reviewed with the git diff option --color-moved=dimmed-zebra
* Merge #17002: chainparams: Bump assumed chain paramsfanquake2019-10-021-2/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fa3a7331160d1a460b1c15fca1810e98070d629c chainparams: Bump assumed chain params (MarcoFalke) Pull request description: As every year, reviewers get extra point when their node is running: * `assumevalid=0` * `checkpoints=0` * on non-x86_64 hardware See https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#before-every-major-and-minor-release for the process. ACKs for top commit: laanwj: ACK fa3a7331160d1a460b1c15fca1810e98070d629c Sjors: ACK fa3a7331160d1a460b1c15fca1810e98070d629c for mainnet on macOS 10.14.6. jamesob: ACK https://github.com/bitcoin/bitcoin/pull/17002/commits/fa3a7331160d1a460b1c15fca1810e98070d629c fanquake: ACK fa3a7331160d1a460b1c15fca1810e98070d629c - checked the mainnet values. I have notes on reviewing `assumevalid` updates in [core-review](https://github.com/fanquake/core-review/blob/master/update-assumevalid.md). Tree-SHA512: fc545ba0a7056908040b47076b393d028c1c022967c25a2074752f76f0386ef099a64445da6125117a04418bd7eb0655121bfc94e6f60b7bc2666947491b5228
| * chainparams: Bump assumed chain paramsMarcoFalke2019-10-011-2/+2
| |
* | doc: Bump version in bips.md, mention bumping in release processWladimir J. van der Laan2019-10-011-1/+1
|/
* Merge #15459: doc: add how to calculate blockchain and chainstate size ↵Wladimir J. van der Laan2019-09-301-1/+21
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | variables to release process eb4c43e49f625895670866b89bb56ca641c4eeb7 doc: documents how to calculate m_assumed_blockchain_size and m_assumed_chain_state_size on the release process. (marcoagner) Pull request description: Regarding [this](https://github.com/bitcoin/bitcoin/pull/15183#issuecomment-463133734) on https://github.com/bitcoin/bitcoin/pull/15183. Added an "Additional information" section for this which seems reasonable to me but may not be the best place for this. Also, let me know if anything else should be documented here (like more details). ACKs for top commit: laanwj: ACK eb4c43e49f625895670866b89bb56ca641c4eeb7 Tree-SHA512: 7e6fc46740daa01dd9be5a8da7846e7a9f7fa866bf31fdc2cb252f90c698cfd6ef954f9588f7abcebda2355ec2b2a380635e14a164e53e77d38abefa3e2cc698
| * doc: documents how to calculate m_assumed_blockchain_size and ↵marcoagner2019-03-201-1/+21
| | | | | | | | m_assumed_chain_state_size on the release process.
* | doc: Remove explicit mention of version from SECURITY.mdMarcoFalke2019-06-141-2/+3
| |
* | doc: update release process with SECURITY.mdJon Atack2019-06-071-0/+2
| |
* | Add riscv64 to outputs list in release-process.mdJeremyRand2019-06-031-0/+1
| | | | | | | | | | The riscv64 binary is created by the Gitian scripts and distributed by the Bitcoin Core website, so it should be listed in the release process docs.
* | doc: add bitcoin_config.h PACKAGE updates to release processJon Atack2019-05-231-4/+4
| | | | | | | | | | | | and reorganise the section and add relative url links. Follow-up to e47dc4f.
* | [docs] Update release-process.mdJon Atack2019-05-101-15/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Create a release notes draft wiki for collaborative editing at https://github.com/bitcoin-core/bitcoin-devwiki/wiki as seen for releases 0.17.0 and 0.18.0. - As per http://www.erisian.com.au/bitcoin-core-dev/log-2019-03-28.html#l-342, for the period during which the notes are being edited on the wiki, the version on the branch should be wiped and replaced with a link to the wiki which should be used for all announcements until final. - Before final, remove the "Needs release note" label from relevant PRs/issues and merge the release notes from the wiki into the branch. - Create a pinned meta-issue dedicated to testing the release candidate and communicate it in release announcements where useful. The former is done in practice (e.g. #15555, #14902) and the latter addresses the discussion here: https://x0f.org/web/statuses/101753569204220416. - Adapt and merge the updates in https://github.com/bitcoin/bitcoin/pull/15692. - Update the version numbers in all the examples. - Reorganise the headers in the Branch Updates section.
* | doc: Remove win32 from the release processMarcoFalke2019-05-081-2/+1
| |
* | Remove Windows 32 bit buildMarcoFalke2019-05-031-2/+0
| |
* | Include bitcoin_config.h in release processHennadii Stepanov2019-04-271-5/+10
|/
* doc: Update release process for snap packageMarcoFalke2019-02-261-10/+34
|
* Delete README_osx.md and move its contents into build-osx.mdMartin Erlandsson2019-01-211-1/+1
|
* Merge #14433: Add checksum in gitian build scripts for osslWladimir J. van der Laan2019-01-151-0/+2
|\ | | | | | | | | | | | | | | | | | | 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
| * Add checksum in gitian build scripts for osslTheCharlatan2019-01-091-0/+2
| | | | | | | | | | | | 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.
* | Merge #13216: [Qt] implements concept for different disk sizes on introJonas Schnelli2019-01-111-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * implements different disk sizes for different networks on intromarcoagner2018-10-071-1/+1
| | | | | | | | | | | | | | - 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.
* | http -> httpsDimitris Apostolou2018-11-241-1/+1
| |
* | Update release-process.md to include RC version bumpingAndrew Chow2018-11-011-1/+2
| |
* | doc: RPC documentationKarel Bílek2018-10-041-0/+2
|/
* doc: Improve command to generate list of authors for release notesMitchell Cash2018-07-191-1/+1
| | | | | | | - 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
* doc: Update broken links to now point to gitian-build.pyMitchell Cash2018-07-191-2/+2
|
* contrib: Clone core repo in gitian-buildMarcoFalke2018-07-171-1/+1
|
* Rename “OS X” to the newer “macOS” conventionGiulio Lombardo2018-06-041-11/+11
|
* doc: update bitcoin-dot-org links in release-process.mdfanquake2018-05-301-2/+2
|
* Give hint about gitian not able to downloadkallewoof2018-03-061-1/+3
| | | | 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`.
* doc: SIGNER can contains space inside now.Ken Lee2018-03-061-11/+11
| | | SIGNER can contains space inside now. mentioned in https://github.com/bitcoin/bitcoin/pull/12527#issuecomment-370506416
* Merge #11909: contrib: Replace developer keys with list of pgp fingerprintsWladimir J. van der Laan2018-02-061-4/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * contrib: Replace developer keys with list of pgp fingerprintsMarcoFalke2017-12-171-4/+1
| |
* | Merge #12317: Document method for reviewers to verify chainTxDataWladimir J. van der Laan2018-02-021-1/+1
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | Document method for reviewers to verify chainTxDataJohn Newbery2018-02-021-1/+1
| | | | | | | | | | | | | | | This commit adds the final block hash of the window to getchaintxstats and documents how reviewers can verify changes to chainTxData.
* | | Merge #12283: Fix typosMarcoFalke2018-02-021-1/+1
|\ \ \ | |/ / |/| | | | | | | | | | | | | | | | | | | | | | | 1340eda3b7 Fix typos (practicalswift) Pull request description: Fix typos. Tree-SHA512: 533a136831387ef26e9a74ba078437496bee38cc026da73fa9e6f6e7f4d5665eccac24cf3ef05e6d3af1329a1214f5ce71b039ddb8378b074e6d4408b8701f95
| * | Fix typospracticalswift2018-01-281-1/+1
| |/
* / doc: Explain how to update chainTxData in release processWladimir J. van der Laan2018-01-311-1/+2
|/ | | | | Adds a short explanation how to update chainTxData to the release process. Mention where to get the data, and link to an example.
* Add instructions for multi-processor gitian buildsCharlie Lee2017-08-131-3/+3
|
* doc: Update release process for simplified version bumpingWladimir J. van der Laan2017-04-061-18/+3
|
* Merge #9734: Add updating of chainTxData to release processWladimir J. van der Laan2017-03-201-0/+1
|\ | | | | | | | | | | 41b8821 Add updating of chainTxData to release process (Pieter Wuille) Tree-SHA512: f7d6e72b19aa83fc4851a9316d6c6a236e0e914d637525cda42c0b15a94543b8072ce67b57d6b12141332a03b64b6c715dff4d61e6e58e0197b22305b35ad65d
| * Add updating of chainTxData to release processPieter Wuille2017-02-091-0/+1
| |
* | Merge #9514: release: Windows signing scriptWladimir J. van der Laan2017-03-131-1/+32
|\ \ | |/ |/| | | | | | | | | | | 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
generated by cgit v1.2.3 (git 2.25.1) at 2026-04-20 08:11:52 +0000