From 8ff171262a4e07563068a1050ebf28bd02d42869 Mon Sep 17 00:00:00 2001 From: MarcoFalke Date: Wed, 31 Jan 2018 08:48:51 -0500 Subject: [PATCH] Merge #12309: doc: Explain how to update chainTxData in release process 7f968ae107 doc: Explain how to update chainTxData in release process (Wladimir J. van der Laan) Pull request description: Adds a short explanation how to update chainTxData to the release process. Mention where to get the data, and link to an example. Tree-SHA512: 66b0eb12a25afb7b1da0788c8f9f9701d566cb7ce55899402440a57bef0e177b55e926442d3c8aa482299abe7c48ab94735d501c37f0a11fefb86e2fc2e33d9b --- doc/release-process.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/release-process.md b/doc/release-process.md index 18acc1a98e..c3b322d720 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -21,7 +21,8 @@ Before every major release: * Update hardcoded [seeds](/contrib/seeds/README.md). TODO: Give example PR for Dash * Update [`BLOCK_CHAIN_SIZE`](/src/qt/intro.cpp) to the current size plus some overhead. -* Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate. +* Update `src/chainparams.cpp` chainTxData with statistics about the transaction count and rate. Use the output of the RPC `getchaintxstats`, see + [this pull request](https://github.com/bitcoin/bitcoin/pull/12270) for an example. * Update version of `contrib/gitian-descriptors/*.yml`: usually one'd want to do this on master after branching off the release - but be sure to at least do it before a new major release ### First time / New builders