08:08 <bitcoin-git> [bitcoin] hebasto opened pull request #26190: build: Disable noisy `-Wreturn-type` for MinGW-w64 (master...220928-return) https://github.com/bitcoin/bitcoin/pull/26190

08:34 <kouloumos> Regarding testing the release candidates, several people reached out to ask if they could test the release candidate by upgrading their existing infrastructure. What, if any, are some precautions that they should take before doing this? I've mentioned wallet backups. Is there anything else? Or in general, something else that people should have in mind when doing this type of upgrade/testing?

08:35 <kouloumos> I am now thinking to add a section in the testing guide talking explicitly about this type of testing, so any suggestions would be helpful.

10:20 <bitcoin-git> [bitcoin] hebasto closed pull request #26190: build: Disable noisy `-Wreturn-type` for MinGW-w64 (master...220928-return) https://github.com/bitcoin/bitcoin/pull/26190

10:54 <bitcoin-git> [bitcoin] R-Y-M-R opened pull request #26191: Docs: grammarly check (master...docs-improve-grammar) https://github.com/bitcoin/bitcoin/pull/26191

13:15 <bitcoin-git> [bitcoin] aureleoules opened pull request #26192: rpc: Improve error when wallet is already loaded (master...2022-09-load-wallet-err) https://github.com/bitcoin/bitcoin/pull/26192

13:18 <instagibbs> kouloumos, ideally whoever is doing this already has upgrade procedures for other dependencies. first update integration tests, then internal environmetn, then testnet, etc

13:18 <instagibbs> maybe stop short of prod for an RC :)

13:29 <kouloumos> Maybe by reffering to it as "existing infrastructure" I made it sound too formal/part of a sophisticated setup. I was mostly referring to regular people running a node at home, not necessarily developers but technical. Somebody that is running the latest release, maybe has an electrum integration, etc. And wants to contribute to the testing efforts by running the release candidate instead of just waiting for v24.0 to

13:29 <kouloumos> come out.

15:15 <bitcoin-git> [bitcoin] w0xlt opened pull request #26194: rpc, wallet: use the same `next_index` key in `listdescriptors` and `importdescriptors` (master...next_index_listdescriptors) https://github.com/bitcoin/bitcoin/pull/26194

15:23 <bitcoin-git> [bitcoin] glozow pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/9fcdb9f3a044...b2da6dd94329

15:23 <bitcoin-git> bitcoin/master faeea28 MacroFake: test: Avoid race in disconnect_nodes helper

15:23 <bitcoin-git> bitcoin/master b2da6dd glozow: Merge bitcoin/bitcoin#26138: test: Avoid race in disconnect_nodes helper

15:23 <bitcoin-git> [bitcoin] glozow merged pull request #26138: test: Avoid race in disconnect_nodes helper (master...2209-test-race-🍄) https://github.com/bitcoin/bitcoin/pull/26138

17:59 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #26195: ci: Use git2.34 for lint task (master...2209-lint-git-🗞) https://github.com/bitcoin/bitcoin/pull/26195

18:24 <bitcoin-git> [bitcoin] theuni opened pull request #26196: kernel: move RunCommandParseJSON to its own file (master...kernel-no-boost-process) https://github.com/bitcoin/bitcoin/pull/26196

18:59 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #26197: [24.x] test: Avoid race in disconnect_nodes helper (24.x...2209-test-race-🍄) https://github.com/bitcoin/bitcoin/pull/26197

20:57 <bitcoin-git> [bitcoin] fanquake opened pull request #26198: refactor: move Boost Datetime usage to wallet (master...move_wallet_boost_out) https://github.com/bitcoin/bitcoin/pull/26198

21:43 <bitcoin-git> [bitcoin] mzumsande opened pull request #26199: p2p: Don't self-advertise during version processing (master...202209_advertise_once) https://github.com/bitcoin/bitcoin/pull/26199