docs: Remove release 28.0 release notes fragments

doc/release-28984.md

@@ -1,6 +0,0 @@
-P2P and network changes
------------------------
-
-- Limited package RBF is now enabled, where the proposed conflicting package would result in
-  a connected component, aka cluster, of size 2 in the mempool. All clusters being conflicted
-  against must be of size 2 or lower.

doc/release-notes-22729.md

@@ -1,21 +0,0 @@
-Notable changes
-===============
-
-P2P and network changes
------------------------
-
-- Previously if Bitcoin Core was listening for P2P connections, either using
-  default settings or via `bind=addr:port` it would always also bind to
-  `127.0.0.1:8334` to listen for Tor connections. It was not possible to switch
-  this off, even if the node didn't use Tor. This has been changed and now
-  `bind=addr:port` results in binding on `addr:port` only. The default behavior
-  of binding to `0.0.0.0:8333` and `127.0.0.1:8334` has not been changed.
-
-  If you are using a `bind=...` configuration without `bind=...=onion` and rely
-  on the previous implied behavior to accept incoming Tor connections at
-  `127.0.0.1:8334`, you need to now make this explicit by using
-  `bind=... bind=127.0.0.1:8334=onion`. (#22729)
-
-- Bitcoin Core will now fail to start up if any of its P2P binds fail, rather
-  than the previous behaviour where it would only abort startup if all P2P
-  binds had failed. (#22729)

doc/release-notes-27101.md

@@ -1,6 +0,0 @@
-JSON-RPC
---------
-
-The JSON-RPC server now recognizes JSON-RPC 2.0 requests and responds with
-strict adherence to the [specification](https://www.jsonrpc.org/specification).
-See [JSON-RPC-interface.md](/doc/JSON-RPC-interface.md#json-rpc-11-vs-20) for details.

doc/release-notes-27114.md

@@ -1,2 +0,0 @@
-- Additional flags "in" and "out" have been added to `-whitelist` to control whether
-  permissions apply to incoming connections and/or manual (default: incoming only).

doc/release-notes-27307.md

@@ -1,8 +0,0 @@
-Wallet
----
-
-The wallet now detects when wallet transactions conflict with the mempool. Mempool
-conflicting transactions can be seen in the `"mempoolconflicts"` field of
-`gettransaction`. The inputs of mempool conflicted transactions can now be respent
-without manually abandoning the transactions when the parent transaction is dropped
-from the mempool, which can cause wallet balances to appear higher.

doc/release-notes-27375.md

@@ -1,6 +0,0 @@
-P2P
----
-
-UNIX domain sockets can now be used for proxy connections. Set `-onion` or `-proxy`
-to the local socket path with the prefix `unix:` (e.g. `-onion=unix:/home/me/torsocket`).
-(#27375)

doc/release-notes-27679.md

@@ -1,2 +0,0 @@
-- unix socket paths are now accepted for `-zmqpubrawblock` and `-zmqpubrawtx` with
-the format `-zmqpubrawtx=unix:/path/to/file`

doc/release-notes-28052.md

@@ -1,6 +0,0 @@
-Blockstorage
-============
-
-Block files are now XOR'd by default with a key stored in the blocksdir.
-Previous releases of Bitcoin Core or previous external software will not be able to read the blocksdir with a non-zero XOR-key.
-Refer to the `-blocksxor` help for more details.

doc/release-notes-29091-29165.md

@@ -1,5 +0,0 @@
-Build
------
-
-GCC 11.1 or later, or Clang 16.0 or later,
-are now required to compile Bitcoin Core.

doc/release-notes-29496.md

@@ -1,11 +0,0 @@
-Mempool Policy Changes
-----------------------
-
-- Transactions with version number set to 3 are now treated as standard on all networks (#29496),
-  subject to Opt-in Topologically Restricted Until Confirmation (TRUC) Transactions policy as
-  described in [BIP 431](https://github.com/bitcoin/bips/blob/master/bip-0431.mediawiki).  The
-  policy includes limits on spending unconfirmed outputs (#28948), eviction of a previous descendant
-  if a more incentive-compatible one is submitted (#29306), and a maximum transaction size of 10,000vB
-  (#29873). These restrictions simplify the assessment of incentive compatibility of accepting or
-  replacing TRUC transactions, thus ensuring any replacements are more profitable for the node and
-  making fee-bumping more reliable.

doc/release-notes-29612.md

@@ -1,8 +0,0 @@
-RPC
----
-
-- The `dumptxoutset` RPC now returns the UTXO set dump in a new and
-  improved format. At the same time the `loadtxoutset` RPC now
-  expects this new format in dumps it tries to load. Dumps with the
-  old format are no longer supported and need to be recreated using
-  the new format in order to be usable.

doc/release-notes-29775.md

@@ -1,10 +0,0 @@
-Testnet4/BIP94 support
------
-
-Support for Testnet4 as specified in [BIP94](https://github.com/bitcoin/bips/blob/master/bip-0094.mediawiki)
-has been added. The network can be selected with the `-testnet4` option and
-the section header is also named `[testnet4]`.
-
-While the intention is to phase out support for Testnet3 in an upcoming
-version, support for it is still available via the known options in this
-release.

doc/release-notes-29845.md

@@ -1,8 +0,0 @@
-RPC
----
-
-- the `warnings` field in `getblockchaininfo`, `getmininginfo` and
-  `getnetworkinfo` now returns all the active node warnings as an array
-  of strings, instead of just a single warning. The current behaviour
-  can temporarily be restored by running bitcoind with configuration
-  option `-deprecatedrpc=warnings`.

doc/release-notes-29987.md

@@ -1,6 +0,0 @@
-Compatibility
-=============
-
-The minimum required glibc to run Bitcoin Core is now
-2.31. This means that RHEL 8 and Ubuntu 18.04 (Bionic)
-are no-longer supported. (#29987)

doc/release-notes-30058.md

@@ -1,7 +0,0 @@
-- When running with -alertnotify, an alert can now be raised multiple
-times instead of just once. Previously, it was only raised when unknown
-new consensus rules were activated, whereas the scope has now been
-increased to include all kernel warnings. Specifically, alerts will now
-also be raised when an invalid chain with a large amount of work has
-been detected. Additional warnings may be added in the future.
-(#30058)

doc/release-notes-30192.md

@@ -1,6 +0,0 @@
-Build
------
-
-`--enable-lcov-branch-coverage` has been removed, given
-incompatibilities between lcov version 1 & 2. `LCOV_OPTS`
-should be used to set any options instead.

doc/release-notes-30212.md

@@ -1,8 +0,0 @@
-RPC
----
-
-- Previously when using the `sendrawtransaction` rpc and specifying outputs
-  that are already in the UXTO set an RPC error code `-27` with RPC error
-  text "Transaction already in block chain" was returned in response.
-  The help text has been updated to "Transaction outputs already in utxo set"
-  to more accurately describe the source of the issue.

doc/release-notes-30275.md

@@ -1,7 +0,0 @@
-RPC
----
-
-- The default mode for the `estimatesmartfee` RPC has been updated from `conservative` to `economical`.
-  which is expected to reduce overestimation for many users, particularly if Replace-by-Fee is an option.
-  For users that require high confidence in their fee estimates at the cost of potentially overestimating,
-  the `conservative` mode remains available.

doc/release-notes-30352.md

@@ -1,10 +0,0 @@
-P2P and network changes
------------------------
-
-- Pay To Anchor(P2A) is a new standard witness output type for spending,
-  a newly recognised output template. This allows for key-less anchor
-  outputs, with compact spending conditions for additional efficiencies on
-  top of an equivalent `sh(OP_TRUE)` output, in addition to the txid stability
-  of the spending transaction.
-  N.B. propagation of this output spending on the network will be limited
-  until a sufficient number of nodes on the network adopt this upgrade.

doc/release-notes-30482.md

@@ -1,6 +0,0 @@
-Updated REST APIs
------------------
-- Parameter validation for `/rest/getutxos` has been improved by rejecting
-  truncated or overly large txids and malformed outpoint indices by raising an
-  HTTP_BAD_REQUEST "Parse error". Previously, these malformed requests would be
-  silently handled. (#30482, #30444)

doc/release-notes-30493.md

@@ -1,4 +0,0 @@
-Full Replace-By-Fee
-===================
-
-`mempoolfullrbf=1` is now set by default.

doc/release-notes-30647.md

@@ -1,4 +0,0 @@
-Tests
------
-
-- The BIP94 timewarp attack mitigation is now active on the `regtest` network

doc/release-notes/release-notes-27064.md

@@ -1,7 +0,0 @@
-Files
------
-
-The default data directory on Windows has been moved from `C:\Users\Username\AppData\Roaming\Bitcoin`
-to `C:\Users\Username\AppData\Local\Bitcoin`. Bitcoin Core will check the existence
-of the old directory first and continue to use that directory for backwards
-compatibility if it is present.