docs: add v20.0.0 release notes, archive v19.3.0 and drop partial ones #5674
Conversation
| @@ -36,49 +36,429 @@ reindex or re-sync the whole chain. | |||
|
|
|||
| # Notable changes | |||
There was a problem hiding this comment.
Some of these are no longer relevant for v20, right? (updated product brief: https://www.dash.org/blog/dashcore-v20-0-product-brief/)
doc/release-notes.md
Outdated
| rewards will change to 20% and 60% respectively upon activation of the change, | ||
| previous reallocation periods are ignored. | ||
|
|
||
| ## Enhanced hard fork |
There was a problem hiding this comment.
it's fully implemented and activated via v20 afaik
There was a problem hiding this comment.
Semantics perhaps. I guess it's implemented, but not going to be used for anything on mainnet in v20? #5642
| enabled by the `v20` activation and `SPORK_24_EHF` spork (__TODO__: is this true?) and will be used for | ||
| the `mn_rr` hard fork. | ||
|
|
||
| ## Asset lock and unlock transactions |
There was a problem hiding this comment.
Almost the same, fully implemented but only "lock" part is activated in v20. Tweaked it a bit.
|
|
||
| - `testmempoolaccept` and `sendrawtransaction` no longer return the P2P `REJECT` | ||
| code when a transaction is not accepted to the mempool. They still return the | ||
| verbal reject reason. |
There was a problem hiding this comment.
Not sure what is meant by "verbal reject reason" 🤔 It returns a message but no error code?
There was a problem hiding this comment.
yes, that's a copy-paste from doc/release-notes-17004.md
UdjinM6
force-pushed
the
rel_notes_20
branch
from
f49ed8c
to
1e3db8d
Compare
|
squashed all the fixes and rebased |
Issue being fixed or feature implemented
NOTE: this PR is for v20.x branch, to be merged as the last one before v20 release.
What was done?
How Has This Been Tested?
Breaking Changes
Checklist: