19:01:17 <laanwj> #startmeeting 19:01:18 <core-meetingbot> Meeting started Thu Jun 24 19:01:17 2021 UTC. The chair is laanwj. Information about MeetBot at https://bitcoin.jonasschnelli.ch/ircmeetings. 19:01:18 <core-meetingbot> Available commands: action commands idea info link nick 19:01:22 <jonasschnelli> hi 19:01:34 <jonatack> hi 19:01:39 <laanwj> #bitcoin -core-dev Meeting: achow101 _aj_ amiti ariard BlueMatt cfields Chris_Stewart_5 darosior digi_james dongcarl elichai2 emilengler fanquake fjahr gleb glozow gmaxwell gwillen hebasto instagibbs jamesob jarolrod jb55 jeremyrubin jl2012 jnewbery jonasschnelli jonatack jtimon kallewoof kanzure kvaciral laanwj lightlike luke-jr maaku marcofalke meshcollider michagogo moneyball morcos 19:01:41 <laanwj> nehan NicolasDorier paveljanik petertodd phantomcircuit promag provoostenator ryanofsky sdaftuar sipa vasild 19:01:48 <fjahr> hi 19:01:50 <achow101> hi 19:01:52 <michaelfolkson> hi 19:01:53 <_aj_> hi 19:01:55 <jarolrod> Hi 19:01:58 <ariard> hi 19:02:23 <dongcarl> hi 19:02:31 <sipa> hi 19:02:33 <laanwj> no proposed meeting topics for this week, any last minute ones? 19:02:41 <kvaciral[m]> hi 19:02:49 <ariard> # super quick coredev update 19:03:30 <laanwj> #topic 22.0 milestone 19:03:31 <core-meetingbot> topic: 22.0 milestone 19:03:46 <achow101> 0.20.2 and 0.21.2? 19:03:50 <laanwj> https://github.com/bitcoin/bitcoin/milestone/47 we're slowly but surely getting through 22.0-tagged PRs 19:04:25 <sipa> yay 19:04:27 <laanwj> #19438 is the largest (code impact wise) feature PR still in there 19:04:29 <gribble> https://github.com/bitcoin/bitcoin/issues/19438 | Introduce deploymentstatus by ajtowns ÷ Pull Request #19438 ÷ bitcoin/bitcoin ÷ GitHub 19:04:33 <sipsorcery> hi 19:06:07 <laanwj> any bugfixes that need to go into 0.22 but aren't tagged yet? 19:07:24 <laanwj> or anything else to discuss wrt 0.22 review 19:08:24 <jonatack> review seems quiet this week. been working on the wallet ones tagged for 22.0, thought it's not code i'm deeply familiar with. 19:08:58 <laanwj> it's been a somewhat quiet week in general 19:09:10 <sipa> the list is shrinking for sure 19:09:16 <sipa> i'll try to review a few more 19:09:27 <Guest30> Hi! 19:09:52 <michaelfolkson> So a week until branch off. Probably a good week to do some reviewing :) 19:10:08 <michaelfolkson> July 1st 19:10:10 <Guest30> I'm new to this community and this meeting, what kind of topics are on the agenda for today? 19:10:25 <michaelfolkson> Guest30: I'll answer your questions afterwards 19:11:05 <Guest30> Thank you :) 19:11:06 <laanwj> michaelfolkson: i doubt that's the day we're going to branch off things have been delayed a bit 19:11:11 <michaelfolkson> Guest30: topic: 22.0 milestone mainly 19:11:42 <michaelfolkson> Oh right feature freeze slipped a few days 19:11:48 <laanwj> but yes it is a good week for some reviewing 19:11:59 <laanwj> nevertheless :) 19:12:07 <sipa> hey we're making progress 19:12:16 <jonatack> always is 19:13:02 <laanwj> #topic Super quick coredev update (ariard) 19:13:02 <core-meetingbot> topic: Super quick coredev update (ariard) 19:13:06 <ariard> hi 19:13:24 <ariard> so a 1st feedback after last week, end of august is likely going to be too short to orga 19:13:39 <ariard> october/november seem more realist, ideally around block 709632 19:14:06 <ariard> and list of countries so far: south france/switzerland/portugal/praha/med country 19:14:07 <michaelfolkson> I'm biased but Advancing Bitcoin might be a good candidate conference. Especially as it would want some Core devs to speak and is more technical 19:14:12 <laanwj> agree, oct/nov is more realistic 19:14:21 <achow101> michaelfolkson: when's that? 19:14:30 <ariard> michaelfolkson: yes though date has been not fixed yet, afaict 19:14:38 <sipa> where is advancing bitcoin? 19:14:38 <michaelfolkson> Either later this year or early next year 19:15:01 <michaelfolkson> I've contacted the organizer (Leon) and will hopefully hear back soon 19:15:04 <sipa> well hard to plan things without knowing a date 19:15:14 <michaelfolkson> Right, I'm chasing :) 19:15:15 <jonatack> after oct we may see renewed restrictions if it's anything like last year 19:15:24 <jonasschnelli> yes... probably 19:15:32 <jonasschnelli> winter / cold / flu season 19:15:46 <sipa> seems unlikely with the way vaccination is going in many places 19:15:51 <sipa> on the other hand, who the hell knows 19:16:01 <ariard> jonatack: that's a good point, thouhg if coredev is scheduled for nov, and restrictions happen beginning of oct 19:16:06 <jonasschnelli> I wound't set it mandatory to organise it around an existing conf. Sure. would be better. But IMO works also standalone 19:16:14 <ariard> we have enough time to work on fallback plan 19:16:25 <jonatack> my guess is there's a semi-sure window in sept/oct, after all bets are off 19:16:50 <ariard> one point to do it in standalone we can do it in nature (sea/mountain) instead of in a big city like london 19:17:23 <jonatack> ariard: provided there is nearby international airport with decent connections 19:17:28 <michaelfolkson> Yeah depends if you want a technical conference or not to organize around 19:17:41 <michaelfolkson> I guess could organize an adhoc conference in nature 19:18:09 <ariard> jonatack: yes international airport for sure! 19:19:04 <ariard> anyway, moving forward on this and if we hit renewed restrictions at autumn, i'll try to figure out a fallback plan (in the limit of possible) 19:19:33 <laanwj> thanks ariard 19:19:36 <michaelfolkson> You're the self volunteered organizer ariard :) I'll let you know if I hear anything re London 19:20:02 <ariard> michaelfolkson: thanks :) 19:20:47 <laanwj> #topic 0.20.2 and 0.21.2 (achow101) 19:20:47 <core-meetingbot> topic: 0.20.2 and 0.21.2 (achow101) 19:21:05 <achow101> we should make 0.20.2 and 0.21.2 at some point 19:21:31 <achow101> we already have 0.20.2rc2, I don't think anything has been added since? 19:21:43 <laanwj> i don't think so 19:21:57 <achow101> only change was updating signapple 19:22:07 <achow101> which I don't think needs another rc 19:22:24 <laanwj> nice, let's just tag 0.20.2 then, it's about time 19:22:33 <laanwj> longest release cycle ever i think :) 19:22:49 <achow101> 0.21.2 would also be nice. 0.21.1 might have gotten less adoption due to the lack of windows cert 19:23:24 <laanwj> and it would be good to get it out before 22.0 release, i think it's impossible to get anyone to care about it after that 19:24:01 <laanwj> what's left to do for 0.21.2? any backport PRs? 19:24:30 <achow101> 2 things https://github.com/bitcoin/bitcoin/milestone/53 19:24:59 <achow101> one backport, one to be backported 19:25:02 <laanwj> #19362 isn't even merged into master yet 19:25:03 <gribble> https://github.com/bitcoin/bitcoin/issues/19362 | rpc/blockchain: Reset scantxoutset progress before inferring descriptors by prusnak ÷ Pull Request #19362 ÷ bitcoin/bitcoin ÷ GitHub 19:25:39 <laanwj> looks like that could block it for a while 19:26:48 <laanwj> i'm actually confused about that one 19:27:31 <laanwj> looks like it has ACKs but isn't merged yet, but was just forgotten for a long time? 19:27:40 <achow101> laanwj: I think it was just forgotten. it's not that complicated 19:28:01 <laanwj> if so it would make sense to move the milestone to 22.0 instead 19:28:23 <laanwj> (and still backport when it's merged of course) 19:28:32 <achow101> sure 19:28:52 <laanwj> done 19:29:48 <laanwj> 0.20.2 does still need release notes before we can tag -final 19:29:59 <laanwj> current release notes on the 0.20 branch are for 0.20.1 19:30:46 <achow101> there's a single release note fragment 19:32:41 <laanwj> ah yes #20861 19:32:44 <gribble> https://github.com/bitcoin/bitcoin/issues/20861 | BIP 350: Implement Bech32m and use it for v1+ segwit addresses by sipa ÷ Pull Request #20861 ÷ bitcoin/bitcoin ÷ GitHub 19:33:37 <bitcoin-git> [bitcoin] sanket1729 opened pull request #22338: Change MAX_OPCODE to OP_CHECKSIGADD (master...opcode_test) https://github.com/bitcoin/bitcoin/pull/22338 19:34:13 <laanwj> ok, so 0.20.2 final is basically ready, waiting for release notes (i'll do the authors and PR list), 0.21.2rc1 is waiting for a backport to be merged and a PR to be merged into master then backported 19:34:21 <laanwj> any other topics? 19:35:10 <laanwj> #endmeeting