16:00:07 <stickies-v> #startmeeting 
16:00:07 <corebot> stickies-v: Meeting started at 2026-10-29T16:00+0000
16:00:08 <corebot> stickies-v: Current chairs: stickies-v
16:00:10 <corebot> stickies-v: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting
16:00:11 <corebot> stickies-v: See also: https://hcoop-meetbot.readthedocs.io/en/stable/
16:00:12 <corebot> stickies-v: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast'
16:00:21 <pseudoramdom> hi
16:00:30 <stickies-v> #bitcoin -core-dev Meeting: _aj_ abubakarsadiq achow101 andrewtoth b10c brunoerg cfields danielabrozzoni darosior dzxzg eugenesiegel fanquake fjahr furszy hebasto hodlinator instagibbs janb84 jarolrod johnny9dev jonatack josie jurraca kanzure kevkevin laanwj lightlike l0rinc maflcko marcofleon maxedw Murch pinheadmz provoostenator pseudoramdom ryanofsky sdaftuar sedited sipa sliv3r__ sr_gi stickies-v stringintech
16:00:30 <stickies-v> theStack vasild willcl-ark
16:00:38 <vasild> hi
16:00:40 <willcl-ark> hi
16:00:41 <brunoerg> hi
16:00:41 <lightlike> hi
16:00:43 <yancy> hi
16:00:44 <pseudoramdom> hi
16:00:46 <nervana21> hi
16:00:51 <johnny9dev> Hi
16:00:52 <janb84> hi
16:00:58 <eugenesiegel> hi
16:01:03 <pinheadmz> Yo
16:01:05 <stickies-v> There are no pre-proposed meeting topics this week. Any last minute ones to add?
16:01:09 <hebasto> hi
16:01:33 <instagibbs> hi
16:02:20 <stickies-v> #topic Fuzzing WG Update (eugenesiegel, marcofleon)
16:03:09 <eugenesiegel> no update from my side
16:03:13 <stickies-v> #topic QML GUI WG Update (johnny9dev)
16:03:38 <johnny9dev> Merged in our integration test fixtures
16:04:02 <johnny9dev> We're working through some multi wallet management improvements and threading
16:04:20 <johnny9dev> Once those are in well be ready to focus in building up the staging branch.
16:04:29 <johnny9dev> That's all for now.
16:05:39 <stickies-v> #topic QA WG Update (brunoerg)
16:05:51 <brunoerg> Hi, just uploaded the results of a mutation testing for src/node/blockstorage.cpp, there are some interesting cases, in case anyone wants to see: https://mutanthub.space/projects/bitcoin/bitcoin/code/src/node/blockstorage.cpp?ref=4fe28722a572793da7614734a0c9cc8e1adc751a
16:05:56 <brunoerg> That’s all
16:07:37 <stickies-v> that's all for the working groups! anything else to discuss?
16:08:09 <stickies-v> i think it's pretty impressive how we managed to crank out all those releases this week, kudos to everyone helping out
16:08:23 <yancy> just curious, what exactly is the merge policy or is there one.
16:08:40 <stickies-v> as per https://bitcoincore.org/en/2026/10/28/disclose-tcp-oom/ : going from first report on 2026-10-23 to finishing release on 2026-10-28 must be a record?
16:08:42 <yancy> I've submitted some small patches over the years, but never really been clear on that
16:09:25 <instagibbs> stickies-v +1, good work to everyone including builders for being available to get it done
16:09:36 <yancy> and the user docs on contributing doesn't really say anything of use
16:10:18 <stickies-v> afaic it's not documented explicitly no, it's also really hard to quantify that in exact non-gameable criteria
16:10:23 <stickies-v> *afaik
16:10:28 <yancy> got it
16:10:41 <yancy> in othere projects, there's sort of a two maintaner ack policy sometimes
16:11:03 <stickies-v> despite how quickly and seemingly smooth this release went, i wonder if there are things we can do to make it easier / more automated, so we can continue to quickly publish releases when necessary
16:11:04 <yancy> wasn't sure what it might be in core since I've never observed any pattern
16:11:37 <vasild> yancy: there is _some_ reasoning in CONTRIBUTING.md, under "Decision Making" Process
16:12:13 <yancy> brunoerg these are some interesting mutations.  I feel like this might actully be something an LLM might be good at writing fixes for.
16:12:15 <stickies-v> e.g. i think one unnecessary point of friction is that release notes are reviewed in the PR, and then again during a release. the release is often months after a PR was merged, so almost no one still has good context on that change. i feel like it makes more sense to just only review release notes in the first PR, and then the final release notes is a purely mechanistic aggregation of all those excerpts
16:13:09 <stickies-v> this might require some more (llm-lintable) rules on release notes in PRs, e.g. make sure they are assigned to an appropriate category, are complete, etc
16:13:52 <vasild> stickies-v: +1
16:14:29 <yancy> vasild yeah, I've read that.  I was just looking for feedback on if there was or wasn't a ACK merge policy, and it doesn't sound like there is.
16:15:44 <instagibbs> PRs can sit around for a long time for various reasons
16:16:04 <instagibbs> including lack of attention by reviewers
16:17:19 <yancy> for sure.  Shame reviewers :P
16:17:20 <stickies-v> can't remember the last time i saw a pr that was RFM and then not merged reasonably quickly; it's always lack of review/consensus in my experience
16:19:03 <stickies-v> alright, looks like that's it for this week. thanks everyone
16:19:06 <stickies-v> #endmeeting