Merge #19483: doc: Merge release notes

fa740d4cea doc: move-only release notes (MarcoFalke)
faa3d2eee1 doc: Remove release notes of backports (MarcoFalke)

Pull request description:

ACKs for top commit:
  laanwj:
    ACK fa740d4cea

Tree-SHA512: 86e7077f9050c65b0b33829892aafabbb783a603a1a77932893659bc1071fb2d2a0515662e7e9e6fdfffb59f86bfc41ad74ba6e86d618bf71a6616d9f7a18fa2

doc/release-notes-11413.md

@@ -1,11 +0,0 @@
-Updated or changed RPC
-----------------------
-
-The `bumpfee`, `fundrawtransaction`, `sendmany`, `sendtoaddress`, and `walletcreatefundedpsbt`
-RPC commands have been updated to include two new fee estimation methods "BTC/kB" and "sat/B".
-The target is the fee expressed explicitly in the given form. Note that use of this feature
-will trigger BIP 125 (replace-by-fee) opt-in.
-
-In addition, the `estimate_mode` parameter is now case insensitive for all of the above RPC commands.
-
-The `bumpfee` command now uses `conf_target` rather than `confTarget` in the options.

doc/release-notes-16377.md

@@ -1,9 +0,0 @@
-RPC changes
------------
-- The `walletcreatefundedpsbt` RPC call will now fail with
-  `Insufficient funds` when inputs are manually selected but are not enough to cover
-  the outputs and fee. Additional inputs can automatically be added through the
-  new `add_inputs` option.
-
-- The `fundrawtransaction` RPC now supports `add_inputs` option that when `false`
-  prevents adding more inputs if necessary and consequently the RPC fails.

doc/release-notes-18202.md

@@ -1,8 +0,0 @@
-Low-level RPC Changes
----------------------
-
-- To make RPC `sendtoaddress` more consistent with `sendmany` the following error
-    `sendtoaddress` codes were changed from `-4` to `-6`:
-  - Insufficient funds
-  - Fee estimation failed
-  - Transaction has too long of a mempool chain

doc/release-notes-18594.md

@@ -1,5 +0,0 @@
-## CLI
-
-The `bitcoin-cli -getinfo` command now displays the wallet name and balance for
-each of the loaded wallets when more than one is loaded (e.g. in multiwallet
-mode) and a wallet is not specified with `-rpcwallet`. (#18594)

doc/release-notes-19133.md

@@ -1,7 +0,0 @@
-## CLI
-
-A new `bitcoin-cli -generate` command, equivalent to RPC `generatenewaddress`
-followed by `generatetoaddress`, can generate blocks for command line testing
-purposes. This is a client-side version of the
-[former](https://github.com/bitcoin/bitcoin/issues/14299) `generate` RPC. See
-the help for details. (#19133)

doc/release-notes-19200.md

@@ -1,7 +0,0 @@
-## Wallet
-
-- Backwards compatibility has been dropped for two `getaddressinfo` RPC
-  deprecations, as notified in the 0.20 release notes. The deprecated `label`
-  field has been removed as well as the deprecated `labels` behavior of
-  returning a JSON object containing `name` and `purpose` key-value pairs. Since
-  0.20, the `labels` field returns a JSON array of label names. (#19200)

doc/release-notes-19219.md

@@ -1,23 +0,0 @@
-#### Changes regarding misbehaving peers
-
-Peers that misbehave (e.g. send us invalid blocks) are now referred to as
-discouraged nodes in log output, as they're not (and weren't) strictly banned:
-incoming connections are still allowed from them, but they're preferred for
-eviction.
-
-Furthermore, a few additional changes are introduced to how discouraged
-addresses are treated:
-
-- Discouraging an address does not time out automatically after 24 hours
-  (or the `-bantime` setting). Depending on traffic from other peers,
-  discouragement may time out at an indeterminate time.
-
-- Discouragement is not persisted over restarts.
-
-- There is no method to list discouraged addresses. They are not returned by
-  the `listbanned` RPC. That RPC also no longer reports the `ban_reason`
-  field, as `"manually added"` is the only remaining option.
-
-- Discouragement cannot be removed with the `setban remove` RPC command.
-  If you need to remove a discouragement, you can remove all discouragements by
-  stop-starting your node.

doc/release-notes-19469.md

@@ -1,6 +0,0 @@
-Updated RPCs
-------------
-
-- `getpeerinfo` no longer returns the `banscore` field unless the configuration
-  option `-deprecatedrpc=banscore` is used. The `banscore` field will be fully
-  removed in the next major release. (#19469)

doc/release-notes.md

@@ -87,6 +87,28 @@ Updated RPCs
   whether initial broadcast of the transaction has been acknowledged by a
   peer. `getmempoolancestors` and `getmempooldescendants` are also updated.
 
+- The `bumpfee`, `fundrawtransaction`, `sendmany`, `sendtoaddress`, and `walletcreatefundedpsbt`
+RPC commands have been updated to include two new fee estimation methods "BTC/kB" and "sat/B".
+The target is the fee expressed explicitly in the given form. Note that use of this feature
+will trigger BIP 125 (replace-by-fee) opt-in. (#11413)
+
+- In addition, the `estimate_mode` parameter is now case insensitive for all of
+  the above RPC commands. (#11413)
+
+- The `bumpfee` command now uses `conf_target` rather than `confTarget` in the
+  options. (#11413)
+
+- `getpeerinfo` no longer returns the `banscore` field unless the configuration
+  option `-deprecatedrpc=banscore` is used. The `banscore` field will be fully
+  removed in the next major release. (#19469)
+
+- The `walletcreatefundedpsbt` RPC call will now fail with
+  `Insufficient funds` when inputs are manually selected but are not enough to cover
+  the outputs and fee. Additional inputs can automatically be added through the
+  new `add_inputs` option. (#16377)
+
+- The `fundrawtransaction` RPC now supports `add_inputs` option that when `false`
+  prevents adding more inputs if necessary and consequently the RPC fails.
 
 Changes to Wallet or GUI related RPCs can be found in the GUI or Wallet section below.
 
@@ -109,12 +131,30 @@ Updated settings
 
 Changes to Wallet or GUI related settings can be found in the GUI or Wallet  section below.
 
+Tools and Utilities
+-------------------
+
+- A new `bitcoin-cli -generate` command, equivalent to RPC `generatenewaddress`
+  followed by `generatetoaddress`, can generate blocks for command line testing
+  purposes. This is a client-side version of the
+  former `generate` RPC. See the help for details. (#19133)
+
+- The `bitcoin-cli -getinfo` command now displays the wallet name and balance for
+  each of the loaded wallets when more than one is loaded (e.g. in multiwallet
+  mode) and a wallet is not specified with `-rpcwallet`. (#18594)
+
 New settings
 ------------
 
 Wallet
 ------
 
+- Backwards compatibility has been dropped for two `getaddressinfo` RPC
+  deprecations, as notified in the 0.20 release notes. The deprecated `label`
+  field has been removed as well as the deprecated `labels` behavior of
+  returning a JSON object containing `name` and `purpose` key-value pairs. Since
+  0.20, the `labels` field returns a JSON array of label names. (#19200)
+
 - To improve wallet privacy, the frequency of wallet rebroadcast attempts is
   reduced from approximately once every 15 minutes to once every 12-36 hours.
   To maintain a similar level of guarantee for initial broadcast of wallet
@@ -261,6 +301,15 @@ GUI changes
 Low-level changes
 =================
 
+RPC
+---
+
+- To make RPC `sendtoaddress` more consistent with `sendmany` the following error
+    `sendtoaddress` codes were changed from `-4` to `-6`:
+  - Insufficient funds
+  - Fee estimation failed
+  - Transaction has too long of a mempool chain
+
 Tests
 -----