Add release notes to Github docs to finish up the release announcements.
To Do Still: Mark as 'latest release' on https://github.com/bitcoin/bitcoin/releases w/ short blurb Announcement on bitcoin-core-dev @BitcoinCoreOrg twitter announcement
Add release notes to Github docs to finish up the release announcements.
To Do Still: Mark as 'latest release' on https://github.com/bitcoin/bitcoin/releases w/ short blurb Announcement on bitcoin-core-dev @BitcoinCoreOrg twitter announcement
ACK ca78b4df1914790900c76a2885daf7ce3df1026e - looks like it matches https://github.com/bitcoin/bitcoin/blob/0.21/doc/release-notes.md.
43 | + 44 | +Notable changes 45 | +=============== 46 | + 47 | +Taproot Soft Fork 48 | +-----------------
nit: In https://github.com/bitcoin/bitcoin/blob/0.21/doc/release-notes.md it is ## Taproot Soft Fork and no line of - afterwards
57 | + 58 | +This release includes the ability to pay taproot addresses, although payments to such addresses are not secure until taproot activates. It also includes the ability to relay and mine taproot transactions after activation. Beyond those two basic capabilities, this release does not include any code that allows anyone to directly use taproot. The addition of taproot-related features to Bitcoin Core’s wallet is expected in later releases once taproot activation is assured. 59 | + 60 | +All users, businesses, and miners are encouraged to upgrade to this release (or a subsequent compatible release) unless they object to activation of taproot. If taproot is locked in, then upgrading before block 709632 is highly recommended to help enforce taproot’s new rules and to avoid the unlikely case of seeing falsely confirmed transactions. 61 | + 62 | +Miners who want to activate Taproot should preferably use this release to control their signaling. The getblocktemplate RPC results will automatically be updated to signal once the appropriate start has been reached and continue signaling until the timeout occurs or taproot activates. Alternatively, miners may manually start signaling on bit 2 at any time; if taproot activates, they will need to ensure they update their nodes before block 709632 or non-upgraded nodes could cause them to mine on an invalid chain. See the versionbits FAQ for details.
Why is the text changed? Why are the links removed?
Did a proper 1-1 copy in #21830
Thanks for comments