doc: add how to calculate blockchain and chainstate size variables to release process #15459

 311 | @@ -312,3 +312,22 @@ bitcoin.org (see below for bitcoin.org update instructions).
 312 |    - Create a [new GitHub release](https://github.com/bitcoin/bitcoin/releases/new) with a link to the archived release notes.
 313 |  
 314 |    - Celebrate
 315 | +
 316 | +### Additional information
 317 | +
 318 | +#### How to calculate `m_assumed_blockchain_size` and `m_assumed_chain_state_size`
 319 | +
 320 | +Both variables are used as a guideline for how much space the user needs on their drive in total, not just strictly for the blockchain.

fanquake commented at 9:48 AM on March 2, 2019:

You could mention up here that the node needs to be synced, i.e All values should be taken from a fully synced node., and save repeating it 4 times below.

You could also do the same for adding overhead. i.e Add 5-10% overhead to all values. and save repeating, plus any ambiguity.

marcoagner commented at 6:33 PM on March 2, 2019:

That makes sense. Thanks!

 340 | +### Additional information
 341 | +
 342 | +#### How to calculate `m_assumed_blockchain_size` and `m_assumed_chain_state_size`
 343 | +
 344 | +Both variables are used as a guideline for how much space the user needs on their drive in total, not just strictly for the blockchain.
 345 | +Note that all values values should be taken from a **fully synced** node and have an overhead of 5-10% added on top of its base value.

practicalswift commented at 3:48 PM on March 20, 2019:

Personally I really value values but I'm not valuing values so much that I think it should be repeated repeatedly.

marcoagner commented at 10:37 PM on March 20, 2019:

:rofl: thanks!