docs: add release notes for v22.0.0 #6459
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
UdjinM6
reviewed
Dec 7, 2024
knst
reviewed
Dec 7, 2024
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
knst
reviewed
Dec 7, 2024
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
consider including some minor changes to release notes:
Merge #6444: fix: add platform transfer to "most common" filter
Merge bitcoin-core/gui#740: Show own outputs on PSBT signing window
Merge bitcoin-core/gui#365: Draw "eye" sign at the beginning of watch-only addresses
69a1305 Merge bitcoin-core/gui#309: Add access to the Peers tab from the network icon (Hennadii Stepanov)
Merge bitcoin-core/gui#256: Save/restore column sizes of the tables in the Peers tab
Member
Author
There was a problem hiding this comment.
Any recommended text?
thephez
requested changes
Dec 7, 2024
Collaborator
thephez
left a comment
thephez
left a comment
There was a problem hiding this comment.
@PastaPastaPasta left some review suggestions
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
If including PR number, it should probably be an actual link to the PR for anyone not looking at the releases notes on Github. Do we typically include PR numbers for RPC changes?
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
If including PR number, it should probably be an actual link to the PR for anyone not looking at the releases notes on Github. Do we typically include PR numbers for RPC changes?
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Suggested change
| - **Breaking Change:** If using named parameters, ensure to update them accordingly. | |
| - **Breaking Change:** If using named parameters, make sure to update them accordingly. |
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Suggested change
| - `creditOutputs` entries in various RPCs that output transaction JSON are now shown as objects instead of strings. | |
| - `creditOutputs` entries in various RPCs that output transactions as JSON are now shown as objects instead of strings. |
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
If including PR number, it should be an actual link to the PR for anyone not looking at the release notes on Github.
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
If including PR number, it should be an actual link to the PR for anyone not looking at the release notes on Github.
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Suggested change
| - Starting in protocol version **70235**, The maximum number of compressed block headers that can be requested at once has been increased from **2000** to **8000**. | |
| - Starting in protocol version **70235**, the maximum number of compressed block headers that can be requested at once has been increased from **2000** to **8000**. |
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
It would only be -v2... if passing as cli arg
Suggested change
| - **Enable Encryption:** Users can opt-in to use BIP324 by adding the `-v2transport=1` flag to their Dash Core configuration. | |
| - **Enable Encryption:** Users can opt-in to use BIP324 by adding the `v2transport=1` to their Dash Core configuration. |
PastaPastaPasta
force-pushed
the
doc-add-release-notes
branch
from
36bd638 to
6bfcd71
Compare
PastaPastaPasta
force-pushed
the
doc-add-release-notes
branch
from
6bfcd71 to
75dd914
Compare
thephez
reviewed
Dec 7, 2024
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Suggested change
| - **`quorum platformsign` | |
| - **`quorum platformsign`** |
PastaPastaPasta
force-pushed
the
doc-add-release-notes
branch
from
75dd914 to
21e8a77
Compare
UdjinM6
previously approved these changes
Dec 10, 2024
UdjinM6
left a comment
UdjinM6
left a comment
There was a problem hiding this comment.
utACK 21e8a7767777bb50df644598c58d44e243a8a8b3
thephez
reviewed
Dec 10, 2024
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Should we mention the previous limit?
Suggested change
| - Flat **2000 Dash** per **576 latest blocks**. | |
| - Flat **2000 Dash** per **576 latest blocks**. The previous limit was 1000 Dash. |
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Suggested change
| These release are considered obsolete. Old release notes can be found here: | |
| These releases are considered obsolete. Old release notes can be found here: |
doc/release-notes.md
Outdated
Collaborator
There was a problem hiding this comment.
Suggested change
| - Introduces a new fork `withdrawals` that changes consensus rules. | |
| - Introduces a new fork, `withdrawals`, that changes consensus rules. |
PastaPastaPasta
force-pushed
the
doc-add-release-notes
branch
from
21e8a77 to
3404fa0
Compare
knst
approved these changes
Dec 10, 2024
PastaPastaPasta
added a commit
to PastaPastaPasta/dash
that referenced
this pull request
Dec 10, 2024
3404fa0 docs: add release notes for v22.0.0 (pasta) Pull request description: ## Issue being fixed or feature implemented Release notes for v22 ## What was done? ## How Has This Been Tested? ## Breaking Changes ## Checklist: _Go over all the following points, and put an `x` in all the boxes that apply._ - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ Top commit has no ACKs. Tree-SHA512: b1fca9297814ab3497cc87512eb2a66daff22a17802c6cd87ef9af75c48fbecda8963c332191c3e3e7abdf495817da3e505b12baa646e97d388cb1aee74a67a7
PastaPastaPasta
added a commit
that referenced
this pull request
Dec 10, 2024
c90339e Merge #6459: docs: add release notes for v22.0.0 (pasta) a6f1fc5 Merge #6475: chore: bumped chain assumed sizes based on latest usage (pasta) d7cd9f1 Merge #6464: chore: update man pages for v22 (pasta) 212f91c Merge #6461: docs: update supported versions in SECURITY.md (pasta) 9a8b685 Merge #6460: chore: Translations 2024-12 (pasta) 2f71f4d Merge #6458: chore: bump MIN_MASTERNODE_PROTO_VERSION to latest proto (pasta) Pull request description: ## Issue being fixed or feature implemented Batch of backports going into v22.0.x recently merged into develop ## What was done? See commits ## How Has This Been Tested? compiles ## Breaking Changes see release notes ## Checklist: _Go over all the following points, and put an `x` in all the boxes that apply._ - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ ACKs for top commit: kwvg: utACK c90339e UdjinM6: utACK c90339e Tree-SHA512: 124643d4b17f126c56225269d291672adf567848f440cd33f53358b3f76f0e5cf801c618493e1e24162e00c525a5d43f1bfa461e8928e04e046b37a94d13ae1c
PastaPastaPasta
added a commit
to PastaPastaPasta/dash
that referenced
this pull request
Dec 14, 2024
1c7bfcb chore: set release true (pasta) c90339e Merge dashpay#6459: docs: add release notes for v22.0.0 (pasta) a6f1fc5 Merge dashpay#6475: chore: bumped chain assumed sizes based on latest usage (pasta) d7cd9f1 Merge dashpay#6464: chore: update man pages for v22 (pasta) 212f91c Merge dashpay#6461: docs: update supported versions in SECURITY.md (pasta) 9a8b685 Merge dashpay#6460: chore: Translations 2024-12 (pasta) 2f71f4d Merge dashpay#6458: chore: bump MIN_MASTERNODE_PROTO_VERSION to latest proto (pasta) fa29ed5 Merge dashpay#6456: fix(qt): allow refreshing wallet data without crashing (pasta) 758cd64 Merge dashpay#6452: fix: store ready queues on the mixing masternode (pasta) 395447b Merge dashpay#6451: depends: update 'src/dashbls' to dashpay/bls-signatures@7e747e8a as 62fa665 (pasta) c7b0d80 Merge dashpay#6441: fix: hold wallet shared pointer in CJ Manager/Sessions to prevent concurrent unload (pasta) c074e09 Merge dashpay#6444: fix: add platform transfer to "most common" filter (pasta) cb04114 Merge dashpay#6442: fix: coin selection with `include_unsafe` option should respect `nCoinType` (pasta) db5b53a Merge dashpay#6434: fix: early EHF and buried EHF are indistinguish (pasta) 8b88ff7 Merge dashpay#6414: chore: bump seeds for v22 (pasta) 02ad523 Merge dashpay#6411: chore: update nMinimumChainWork, defaultAssumeValid, checkpointData, chainTxData for mainnet and testnet (pasta) 3bbcd3d Merge dashpay#6393: docs: mention building for some HOSTs only in `release-process.md` (pasta) 18f636f Merge dashpay#6426: fix: respect SENDDSQUEUE message, move DSQ relay into net processing / peerman (pasta) 9fed456 Merge dashpay#6407: fix: dataraces (pasta) 86105da Merge dashpay#6408: refactor: removed pre-MN_RR logic of validation of CL (pasta) a1f7e96 Merge dashpay#6406: ci: use `actions/cache` to manage depends cache (pasta) 90a3807 Merge dashpay#6402: ci: cache built (pasta) 66f6787 Merge dashpay#6401: ci: deduplicate depends building (pasta) 7ca5663 Merge dashpay#6397: ci: add powerpc64 to GH Guix job matrix (pasta) Pull request description: ## Issue being fixed or feature implemented ## What was done? Suppressed changes from 1c7bfcb and resolved merge conflicts. ``` Auto-merging .github/workflows/build.yml Auto-merging configure.ac Auto-merging src/chainparams.cpp Auto-merging src/coinjoin/client.cpp CONFLICT (content): Merge conflict in src/coinjoin/client.cpp Auto-merging src/coinjoin/client.h CONFLICT (content): Merge conflict in src/coinjoin/client.h Auto-merging src/coinjoin/util.cpp CONFLICT (content): Merge conflict in src/coinjoin/util.cpp Auto-merging src/coinjoin/util.h CONFLICT (content): Merge conflict in src/coinjoin/util.h Auto-merging src/evo/specialtxman.cpp Auto-merging src/init.cpp Auto-merging src/net_processing.cpp CONFLICT (content): Merge conflict in src/net_processing.cpp Auto-merging src/net_processing.h Auto-merging src/qt/transactiontablemodel.cpp Auto-merging src/wallet/wallet.cpp Auto-merging src/wallet/wallet.h CONFLICT (content): Merge conflict in src/wallet/wallet.h Auto-merging test/functional/feature_llmq_chainlocks.py CONFLICT (content): Merge conflict in test/functional/feature_llmq_chainlocks.py ``` ## How Has This Been Tested? ## Breaking Changes ## Checklist: - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_ ACKs for top commit: PastaPastaPasta: utACK d108579; no diff to develop Tree-SHA512: 3f063011224880fee35edb04ce265dff33a52273c3d45ef1dbcebcecb22c25d8ad7c91b83514f36142716a6fbd0ddd3a8a3f2a9b59ce78ce975bbce69a2a13b5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
Release notes for v22
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:
Go over all the following points, and put an
xin all the boxes that apply.