💬 ismaelsadeeq commented on pull request "init: make `-blockmaxweight` startup option debug only":
(https://github.com/bitcoin/bitcoin/pull/32654#discussion_r2402298073)
Done https://github.com/bitcoin-core/bitcoin-devwiki/wiki/v30.0-Release-Notes-Draft/3a0ad5b7901c244976eeffb034305614efb350b6

📝 fanquake opened a pull request: "[28.x] More backports"
(https://github.com/bitcoin/bitcoin/pull/33535)
Backports:
* #33504

💬 fanquake commented on pull request "Mempool: Do not enforce TRUC checks on reorg":
(https://github.com/bitcoin/bitcoin/pull/33504#issuecomment-3366152838)
Backported to 28.x in #33535.

💬 fanquake commented on pull request "doc: Add `INSTALL.md` to Linux release tarballs":
(https://github.com/bitcoin/bitcoin/pull/33451#discussion_r2402371308)
`libxcb-cursor` can be removed now.

💬 fanquake commented on pull request "contrib: fix macOS deployment with no translations":
(https://github.com/bitcoin/bitcoin/pull/33482#issuecomment-3366186004)
Backported to `29.x` in #33534.

💬 Christewart commented on issue "v30.0 Testing":
(https://github.com/bitcoin/bitcoin/issues/33368#issuecomment-3366229922)
> > One thing I noticed was the getwalletinfo RPC removed the fields balance, immature_balance, and unconfirmed_balance from the RPC result in [0ec2551](https://github.com/bitcoin/bitcoin/commit/0ec255139be3745a135386e9db957fe81bc3d833). Is this worth a release note?
>
> [@Christewart](https://github.com/Christewart) it was mentioned in the PR: [#32721 (comment)](https://github.com/bitcoin/bitcoin/pull/32721#issuecomment-3006074516). [@achow101](https://github.com/achow101) do you want to add o
...

💬 fanquake commented on issue "v30.0 Testing":
(https://github.com/bitcoin/bitcoin/issues/33368#issuecomment-3366235908)
> I can write it

You can add it here: https://github.com/bitcoin-core/bitcoin-devwiki/wiki/v30.0-Release-Notes-Draft.

💬 instagibbs commented on pull request "[30.x] Backports & rc3":
(https://github.com/bitcoin/bitcoin/pull/33473#issuecomment-3366258734)
ACK on https://github.com/bitcoin/bitcoin/pull/33504 and https://github.com/bitcoin/bitcoin/pull/33504 changes

💬 fanquake commented on pull request "wallet: don't consider unconfirmed TRUC coins with ancestors":
(https://github.com/bitcoin/bitcoin/pull/33528#issuecomment-3366268611)
Is this going to be backported to `30.x`?

💬 davidgumberg commented on pull request "[29.x] Finalise 29.2rc2":
(https://github.com/bitcoin/bitcoin/pull/33534#issuecomment-3366274330)
ACK https://github.com/bitcoin/bitcoin/pull/33534/commits/ca86f3645e1c49d9a2b95c70e475e27f2fc87d4b

I compared this to other PR's (#32766) of the "finalize format", and this has the two finalizing chagnes:
- this bumps the build version in the 29.x branch
- updates the versions in the manpages.

I compared the backport commit https://github.com/bitcoin/bitcoin/pull/33534/commits/6b3c1dbc5c0df4357ee7f57ac238bcdff55526af to https://github.com/bitcoin/bitcoin/pull/33482/commits/7b5261f7ef3d
...

📝 frankomosh opened a pull request: "doc: add coverage instrumentation hint to libFuzzer quickstart"
(https://github.com/bitcoin/bitcoin/pull/33536)
This patch shows how to enable clang source-based coverage instrumentation in the libFuzzer quickstart section. No defaults are changed, and the addition is intended to be optional.

Fixes silent "no .profraw file" confusion/error when trying to generate coverage data.

💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads >10% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r2402470414)
Done.

💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads >10% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r2402470769)
Done.

💬 andrewtoth commented on pull request "validation: fetch block inputs on parallel threads >10% faster IBD":
(https://github.com/bitcoin/bitcoin/pull/31132#discussion_r2402472467)
Added some explanation in the commit message. Please let me know if it makes it more clear.

👋 frankomosh's pull request is ready for review: "doc: add coverage instrumentation hint to libFuzzer quickstart"
(https://github.com/bitcoin/bitcoin/pull/33536)

📝 fanquake converted_to_draft a pull request: "Update libmultiprocess subtree in 30.x branch"
(https://github.com/bitcoin/bitcoin/pull/33519)
Includes:

- https://github.com/bitcoin-core/libmultiprocess/pull/207
- https://github.com/bitcoin-core/libmultiprocess/pull/208
- https://github.com/bitcoin-core/libmultiprocess/pull/211
- https://github.com/bitcoin-core/libmultiprocess/pull/201
- https://github.com/bitcoin-core/libmultiprocess/pull/213
- https://github.com/bitcoin-core/libmultiprocess/pull/214
- https://github.com/bitcoin-core/libmultiprocess/pull/221
- https://github.com/bitcoin-core/libmultiprocess/pull/220

Corre
...

📝 fanquake converted_to_draft a pull request: "Update libmultiprocess subtree to support reduced logging"
(https://github.com/bitcoin/bitcoin/pull/33518)
Includes:

- https://github.com/bitcoin-core/libmultiprocess/pull/213
- https://github.com/bitcoin-core/libmultiprocess/pull/214
- https://github.com/bitcoin-core/libmultiprocess/pull/221
- https://github.com/bitcoin-core/libmultiprocess/pull/220

The last change is needed to support #33517 and fix poor performance in some cases caused by slow logging.

The changes can be verified by running `test/lint/git-subtree-check.sh src/ipc/libmultiprocess` as described in [developer notes](https
...

🤔 glozow reviewed a pull request: "[29.x] Finalise 29.2rc2"
(https://github.com/bitcoin/bitcoin/pull/33534#pullrequestreview-3299962725)
lgtm 513cef75ee06bc5d310a22d366a5f3c815aa1499. Got the same manpages, no changes to examples/bitcoin.conf or bips.md.

I think the release notes need to be updated

💬 glozow commented on pull request "[29.x] Finalise 29.2rc2":
(https://github.com/bitcoin/bitcoin/pull/33534#discussion_r2402655206)
Need to update release notes for #33482, no?

💬 glozow commented on pull request "[29.x] Finalise 29.2rc2":
(https://github.com/bitcoin/bitcoin/pull/33534#discussion_r2402669380)
I also don't see #32989