Oh forgot about the meeting. I was wondering if we can add #16702 to high-prio. If we want to make it to the next release better start early, the change is not big but require reviewers looking into addrman so..
wumpus I saw that earlier and double-checked, I couldn't find any version numbers that were cropped in the macOS release binaries
FYI the verify-commits script was failing for me again. And doing a pull of keys as stated in the readme did not resolve it sadly. Anybody having the same issue? Had trouble getting this key: 262685BC78ED11FB
was on 23cecd6cd56f952c757f469c46d7593c2ffaa419 when running it
there is no maintainer key 262685BC78ED11FB, where did you see it used?
merge commit 23cecd6cd56f952c757f469c46d7593c2ffaa419 is signed by my key
wumpus: I wend to github and checked the key of the commit signed, that is where it said so
I should be able to reproduce that by going back with git reflog to the state the repo was before. I lost patience and just did a git pull
and "git pull" did a fast forward, I suppose? in that case, there's probably nothing fishy going on there