also if you have any last minute meeting topic, of course
if we have nothing else, here's a quick update on assumeutxo: I'm towards the end of a (pretty involved) rebase and will be pushing that up soon. afterwards I'll run manual tests and start on writing some functional tests.
proposed topic: which versions to re-release with new windows code signing cert?
laanwj: you might need to update the meeting ping with few nicknames upgrade :)
ariard: if there's any you'd like to add let me know
laanwj: yours is changed at least
ariard: jonatack good point
#topic High priority for review
topic: High priority for review
g_chainman de-globalization reviewers: Since we're just a few weeks away from feature freeze, I'd love to get bundle 6 in ASAP (bundle 7 will be the last one and removes all review-only assertions)
bitcoin/0.19 461b9b1 Andrew Chow: Update Windows code signing certificate
sorry I've missed this cert stuff. Can anyone give a quick tl;dr of what happened?
cfields: comodo unexpectedly revoked the previous cert when I tried to renew it. Then it was a pain to get a new cert because the validation rules have changed. So we had to make a new LLC for that and it took some time.
[bitcoin] theStack opened pull request #22089: test: MiniWallet: fix fee calculation for P2PK and check tx vsize (master...202105-test-miniwallet-fix_p2pk_fee_calculation) https://github.com/bitcoin/bitcoin/pull/22089
the revocation was retroactive so all of our previous releases signed with that cert now won't install on windows
dongcarl: yes, will look into that soon
ugh, right, I guess timestamped signatures don't help with that by design.
that's very annoying.
nice to see that revocation works as intended though, I guess :p
very good that it works though slightly scary that it can just happen under us arbitarily
happy it's only the installer that is signed, imagine if the actual binary was signed and suddenly was rejected when trying to start it
laanwj: i'm kind of surprised things don't already work that way