You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/release-process.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,19 +14,9 @@ Release Process
14
14
* Update [bips.md](bips.md) to account for changes since the last release (don't forget to bump the version number on the first line).
15
15
* Update version in `configure.ac` (don't forget to set `CLIENT_VERSION_RC` to `0`).
16
16
* Write release notes (see "Write the release notes" below).
17
-
* Update `src/chainparams.cpp` nMinimumChainWork with information from the getblockchaininfo rpc.
18
-
* Update `src/chainparams.cpp` defaultAssumeValid with information from the getblockhash rpc.
19
-
- The selected value must not be orphaned so it may be useful to set the value two blocks back from the tip.
20
-
- Testnet should be set some tens of thousands back from the tip due to reorgs there.
21
-
- This update should be reviewed with a reindex-chainstate with assumevalid=0 to catch any defect
22
-
that causes rejection of blocks in the past history.
23
17
24
18
### Before every major release
25
19
26
-
* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/bitcoin/bitcoin/pull/7415) for an example.
27
-
* Update [`src/chainparams.cpp`](/src/chainparams.cpp) m_assumed_blockchain_size and m_assumed_chain_state_size with the current size plus some overhead (see [this](#how-to-calculate-m_assumed_blockchain_size-and-m_assumed_chain_state_size) for information on how to calculate them).
28
-
* Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate. Use the output of the RPC `getchaintxstats`, see
29
-
[this pull request](https://github.com/bitcoin/bitcoin/pull/17002) for an example. Reviewers can verify the results by running `getchaintxstats <window_block_count> <window_last_block_hash>` with the `window_block_count` and `window_last_block_hash` from your output.
30
20
* On both the master branch and the new release branch:
31
21
- update `CLIENT_VERSION_MINOR` in [`configure.ac`](../configure.ac)
32
22
- update `CLIENT_VERSION_MINOR`, `PACKAGE_VERSION`, and `PACKAGE_STRING` in [`build_msvc/bitcoin_config.h`](/build_msvc/bitcoin_config.h)
@@ -36,6 +26,16 @@ Release Process
36
26
37
27
#### Before branch-off
38
28
29
+
* Update hardcoded [seeds](/contrib/seeds/README.md), see [this pull request](https://github.com/bitcoin/bitcoin/pull/7415) for an example.
30
+
* Update [`src/chainparams.cpp`](/src/chainparams.cpp) m_assumed_blockchain_size and m_assumed_chain_state_size with the current size plus some overhead (see [this](#how-to-calculate-m_assumed_blockchain_size-and-m_assumed_chain_state_size) for information on how to calculate them).
31
+
* Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate. Use the output of the RPC `getchaintxstats`, see
32
+
[this pull request](https://github.com/bitcoin/bitcoin/pull/17002) for an example. Reviewers can verify the results by running `getchaintxstats <window_block_count> <window_last_block_hash>` with the `window_block_count` and `window_last_block_hash` from your output.
33
+
* Update `src/chainparams.cpp` nMinimumChainWork with information from the getblockchaininfo rpc.
34
+
* Update `src/chainparams.cpp` defaultAssumeValid with information from the getblockhash rpc.
35
+
- The selected value must not be orphaned so it may be useful to set the value two blocks back from the tip.
36
+
- Testnet should be set some tens of thousands back from the tip due to reorgs there.
37
+
- This update should be reviewed with a reindex-chainstate with assumevalid=0 to catch any defect
38
+
that causes rejection of blocks in the past history.
39
39
- Clear the release notes and move them to the wiki (see "Write the release notes" below).
0 commit comments