Release Process for v19.0.0

[PastaPastaPasta]

v19.0.0 Release Process

• [x] Update translations, see translation_process.md. (@UdjinM6) https://github.com/dashpay/dash/pull/5208
• [x] Update manpages, see gen-manpages.sh. (@knst)

Before every minor and major release:

• [x] Update bips.md to account for changes since the last release (@thephez).
• [x] Update version in configure.ac (don't forget to set CLIENT_VERSION_IS_RELEASE to true) (@PastaPastaPasta)
• [x] Write Release Notes (@PastaPastaPasta @UdjinM6)
• [x] Update src/chainparams.cpp nMinimumChainWork with information from the getblockchaininfo rpc. (@knst) https://github.com/dashpay/dash/pull/5304
• [x] Update src/chainparams.cpp defaultAssumeValid with information from the getblockhash rpc. (@knst) https://github.com/dashpay/dash/pull/5304
• [x] Update main net activation timing (@ogabrielides) https://github.com/dashpay/dash/pull/5300
• [x] 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. (@ogabrielides) (Checked on both Testnet/Mainnet)
• [ ] Ensure that sentinel is not affected by any changes, and no changes to sentinel are required. (@nmarley @thephez) https://github.com/dashpay/sentinel/pull/116
• [ ] Ensure that governance is functional after sentinel changes are done
• [x] Ensure all TODOs are evaluated and resolved if needed (@PastaPastaPasta to create google sheet of all)
• [ ] Verify insight works (@strophy)
• [ ] Verify p2pool works (unmaintained; no responsible party)

Tag the Release

• [ ] Tag v19.0.0 and push (@PastaPastaPasta)

Check CI

• [ ] Validate that CI passes

Do Gitian Build (for unsigned binaries) and create PRs

• [x] Pasta Gitian Build
• [x] Udjin Gitian Build
• [x] Thephez Gitian Build
• [ ] Kittywhiskers Gitian Build
• [x] Knst Gitian Build

Create Windows/OS X detached signatures (note: it might be decided skip signed binaries for RCs) Only once the Windows/OS X builds each have 3 matching signatures may they be signed with their respective release keys.

• [x] Pasta creates windows detached signature and commits
• [x] pasta creates OS X detached signature

Update Gitian Builds with signed binaries (note: it might be decided skip signed binaries for RCs)

• [x] Pasta Gitian Build
• [x] Udjin Gitian Build
• [x] Thephez Gitian Build
• [ ] Kittywhiskers Gitian Build
• [ ] Knst Gitian Build

After 3 or more people have gitian-built and their results match:

• [x] Create SHA256SUMS.asc for the builds
• [x] GPG sign each download / binary
• [x] Upload zips and installers, as well as SHA256SUMS.asc from last step, to github as github draft release.
• [x] Validate SHA256SUMS.asc and all binaries attached to github draft release are correct
• [ ] Notarize OS X binaries (we can't do this) (talk to @tikhop (pavel) about this
• [x] Release on github
• [ ] Update website
• [ ] Ensure that docker hub images are up to date

Announce the release:

• [x] Release on Dash forum: https://www.dash.org/forum/topic/official-announcements.54/ (Patrick)
• [x] Optionally Discord, twitter, reddit /r/Dashpay, post in slack... but this will usually sort out itself
• [ ] Celebrate

After the release

• [ ] Submit patches to BTCPay to ensure they use latest / compatible version see https://github.com/dashpay/dash/issues/4211#issuecomment-966608207 (@strophy ?)

Additional Items

• [ ] Prepare release blog post (necessary so we have a permalink to use on twitter, reddit, etc.)
• [ ] Prepare product brief (major versions only?) (@thephez; need to talk with marina and publish this asap)
• [ ] Prepare a release announcement tweet (tell Marina)
• [ ] Follow-up tweets with any important block heights for consensus changes (Marina again)
• [ ] Post on reddit
• [ ] Update docs (readme and RTD) (@thephez)
• [ ] Test Docker build runs without errors in Dashmate (@shumkov)
• [ ] Add new Release Process items to in repo release process document (@knst)

[thephez]

@PastaPastaPasta I don't see anything missing from bips.md. The only change in this relates to BIP-61 reject messages and that's already mentioned.

[thephez]

Product brief has been published: https://www.dash.org/news/dashcore-v19-0-product-brief/

[hell0-w]

@PastaPastaPasta Sorry maybe wrong topic, but I need help.

Can you please help with updating image dash with v19.2.0 for btcpayserver ? Dash stuck Ticket LINK Many, Many thanks.

[strophy]

Hi @hell0-w thanks for bringing our attention to this!

It looks like BTCPayServer users are stuck on an invalid block, I'll ask someone to comment on the thread there on how to get back on the right chain.

We also have two PRs open for another upcoming update which will need to be merged and deployed before July 5: https://github.com/btcpayserver/dockerfile-deps/pull/66 https://github.com/btcpayserver/btcpayserver-docker/pull/800

[NicolasDorier]

PRs merged