@@ -18,11 +18,40 @@ infrastructure projects.
1818## Bitcoin Core PR Review Club
1919
2020* In this monthly section, we summarize a recent [ Bitcoin Core PR Review
21- Club] [ ] meeting, highlighting some of the important questions and
22- answers. Click on a question below to see a summary of the answer from
23- the meeting.*
24-
25- FIXME: stickies-v
21+ Club] [ ] meeting.*
22+
23+ [ Testing Bitcoin Core 31.0 Release Candidates] [ review club
24+ v31-rc-testing] was a review club meeting that did not review a
25+ particular PR, but rather was a group testing effort.
26+
27+ Before each [ major Bitcoin Core release] [ ] , extensive testing by the
28+ community is considered essential. For this reason, a volunteer writes a
29+ testing guide for a release candidate so that as many people as
30+ possible can productively test without having to independently ascertain
31+ what's new or changed in the release, and reinvent the various setup
32+ steps to test these features or changes.
33+
34+ Testing can be difficult because when one encounters unexpected
35+ behavior, it's often unclear if it's due to an actual bug or if the
36+ tester is making a mistake. It wastes developers' time to report bugs to
37+ them that aren't real bugs. To mitigate these problems and promote
38+ testing efforts, a Review Club meeting is held for a particular release
39+ candidate.
40+
41+ The [ 31.0 release candidate testing guide] [ 31.0 testing ] was written by
42+ [ svanstaa] [ gh svanstaa ] (see [ Podcast #397 ] [ pod397 v31rc1 ] ), who also hosted the review club meeting.
43+
44+ Attendees were also encouraged to get testing ideas by reading the [ 31.0
45+ release notes] [ ] .
46+
47+ The testing guide covers [ cluster mempool] [ topic cluster mempool ] including new
48+ RPCs and cluster limits (see [ Newsletter #382 ] [ news382 bc33629 ] ), private broadcast
49+ (see [ Newsletter #388 ] [ news388 bc29415 ] ), an updated ` getblock ` RPC with a new ` coinbase_tx ` field
50+ (see [ Newsletter #394 ] [ news394 bc34512 ] ), a new ` txospenderindex ` which tracks which
51+ transaction spends each output (see [ Newsletter #394 ] [ news394 bc24539 ] ), an increased default
52+ ` -dbcache ` size (see [ Newsletter #396 ] [ news396 bc34692 ] ), embedded ASMap data
53+ (see [ Newsletter #394 ] [ news394 bc28792 ] ), and a new REST API ` blockpart ` endpoint
54+ (see [ Newsletter #386 ] [ news386 bc33657 ] ).
2655
2756## Notable code and documentation changes
2857
@@ -101,3 +130,16 @@ repo], and [BINANAs][binana repo]._
101130[ BIP393 ] : https://github.com/bitcoin/bips/blob/master/bip-0393.mediawiki
102131[ BIP440 ] : https://github.com/bitcoin/bips/blob/master/bip-0440.mediawiki
103132[ BIP441 ] : https://github.com/bitcoin/bips/blob/master/bip-0441.mediawiki
133+ [ review club v31-rc-testing ] : https://bitcoincore.reviews/v31-rc-testing
134+ [ major bitcoin core release ] : https://bitcoincore.org/en/lifecycle/#versioning
135+ [ 31.0 release notes ] : https://github.com/bitcoin-core/bitcoin-devwiki/wiki/31.0-Release-Notes-Draft
136+ [ 31.0 testing ] : https://github.com/bitcoin-core/bitcoin-devwiki/wiki/31.0-Release-Candidate-Testing-Guide
137+ [ gh svanstaa ] : https://github.com/svanstaa
138+ [ pod397 v31rc1 ] : /en/podcast/2026/03/24/#bitcoin-core-31-0rc1-transcript
139+ [ news382 bc33629 ] : /en/newsletters/2025/11/28/#bitcoin-core-33629
140+ [ news388 bc29415 ] : /en/newsletters/2026/01/16/#bitcoin-core-29415
141+ [ news394 bc34512 ] : /en/newsletters/2026/02/27/#bitcoin-core-34512
142+ [ news394 bc24539 ] : /en/newsletters/2026/02/27/#bitcoin-core-24539
143+ [ news396 bc34692 ] : /en/newsletters/2026/03/13/#bitcoin-core-34692
144+ [ news394 bc28792 ] : /en/newsletters/2026/02/27/#bitcoin-core-28792
145+ [ news386 bc33657 ] : /en/newsletters/2026/01/02/#bitcoin-core-33657
0 commit comments