Release process for 0.19.0 #16996

issue laanwj opened this issue on September 30, 2019
  1. laanwj commented at 12:45 PM on September 30, 2019: member

    Before 0.19 split-off

    • Update bips.md to account for changes since the last release (#16997).
    • Update hardcoded seeds (#16999).
    • Update src/chainparams.cpp (#17002)
      • nMinimumChainWork with information from the getblockchaininfo rpc.
      • defaultAssumeValid with information from the getblockhash rpc.
        • The selected value must not be orphaned so it may be useful to set the value two blocks back from the tip.
        • Testnet should be set some tens of thousands back from the tip due to reorgs there.
        • This update should be reviewed with a reindex-chainstate with assumevalid=0 to catch any defect that causes rejection of blocks in the past history.
      • m_assumed_blockchain_size and m_assumed_chain_state_size with the current size plus some overhead (see this for information on how to calculate them).
      • chainTxData with statistics about the transaction count and rate. Use the output of the RPC getchaintxstats, see this pull request 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.

    After 0.19 split-off, before rc1

    • Collect release notes fragments, put release notes on wiki
    • On both the master branch and the new release branch (#17007 for master):
    • On the new release branch in configure.ac and build_msvc/bitcoin_config.h (see this commit):
      • set CLIENT_VERSION_REVISION to 0
      • set CLIENT_VERSION_IS_RELEASE to true
    • Bump gitian descriptor version on master (#17049)

    Release candidates done

    • rc1
    • rc2 (doa)
    • rc3

    Before every release candidate

    Before -final

    • Finalize release notes #17403
    • Update version in configure.ac (don't forget to set CLIENT_VERSION_RC to 0).
  2. laanwj added this to the milestone 0.19.0 on Sep 30, 2019
  3. laanwj pinned this on Sep 30, 2019
  4. fanquake commented at 12:43 AM on October 1, 2019: member

    Collect release notes fragments, put release notes on wiki

    We need to remember to address this comment from @jb55.

  5. MarcoFalke commented at 1:19 AM on October 1, 2019: member

    @harding Have you been working on this #16690 (review) ?

  6. laanwj commented at 9:27 AM on October 2, 2019: member

    The last PRs blocking the 0.19 split-off are : #16999 #16952 #16849 #16727

  7. laanwj commented at 10:14 AM on October 2, 2019: member
  8. MarcoFalke commented at 2:07 PM on October 2, 2019: member

    Moved release notes :rocket:

  9. laanwj referenced this in commit ecc0f272a0 on Oct 2, 2019
  10. laanwj renamed this:
    Release process for 0.19.0rc1
    Release process for 0.19.0
    on Oct 9, 2019
  11. fanquake deleted a comment on Oct 21, 2019
  12. MarcoFalke added the label Needs release note on Nov 6, 2019
  13. MarcoFalke commented at 1:30 PM on November 6, 2019: member

    Anyone want to fix this: #16957 (comment) ?

  14. laanwj commented at 1:39 PM on November 6, 2019: member

    I found it very hard to describe the change (because the same dbcache value uses less real memory…). Something like:?

    The chainstate takes about 9% less memory, at the same time making -dbcache accounting more accurate (it was underestimating the use of memory before). This has the effect that -dbcache can be increased from say, 450 in previous versions to 500 in this versions with the same real memory use, but have more cache available for increased performance.

  15. harding commented at 6:55 PM on November 6, 2019: contributor
  16. laanwj commented at 7:49 PM on November 6, 2019: member

    @harding LGTM, thanks!

  17. MarcoFalke removed the label Needs release note on Nov 6, 2019
  18. MarcoFalke commented at 8:32 PM on November 6, 2019: member

    Anything left to do for the release or is it good to go?

  19. laanwj commented at 9:35 PM on November 6, 2019: member

    I don't think so, maybe we should discuss in the meeting tomorrow.

  20. laanwj unpinned this on Nov 10, 2019
  21. laanwj closed this on Nov 10, 2019

  22. DrahtBot locked this on Dec 16, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 15:14 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me