00:16:35 It would be nice if the fuzz PR (6535) could be reviewed within the next week or so. It's a prerequisite for getting the fuzz tests to run on OSS-fuzz, and I'd like to get monero committed there in case they change their mind about it :) 00:17:35 (it gets us (presumably) lots of CPU time fuzzing our stuff. 00:18:51 * moneromooo feels a bit like a hypocrit using some goggle stuff when they're such a privacy problem but hey. So be it. 00:47:23 luigi1111w: are you available in the next days for tagging / release? 01:01:52 yes 01:01:58 till thursday ish 07:29:11 translators are still submitting strings, but please let me know when we are out of time and i will PR the translations we got 12:14:30 Dev meeting tonight to discuss the finalization of the release? 12:47:45 ok for me 17:04:17 Who is available for a meeting? 17:04:24 yes 17:04:29 Here 17:04:30 sorry, I got out of step 17:04:32 want me to run? 17:04:35 or you got this? 17:07:18 yep 17:07:42 here 17:09:34 First we have 2 moderators, and now none :) 17:09:45 still here 17:10:24 Whoever has something to ask or ask, just do say/ask :) 17:10:27 remaining PRs before tagging: #6532 #6540 #6541 #6543 #6545 #6548 #6551 17:10:35 plus one that mooo is still working on 17:11:00 Sorry about the last minute, just got told today. 17:11:12 Simple enough though. 17:11:15 do you think you can get it ready today? 17:11:19 Yes. 17:11:23 ok 17:11:52 there are quite a few reviews missing so I think we will tag tomorrow anyway 17:12:12 I got #6549 for master sorted now with the help of moneromooo. Will have to push #6548 through the same process, which I should be able to do later today 17:12:35 ErCiccione[m]: can you PR GUI translations tomorrow? 17:13:02 Sure thing 17:13:35 I'll have to set up a new environment to test the GUI, then i'll make a release of the GUI guide 17:13:39 anything else missing? 17:13:57 CSAG :( 17:14:01 CLSAG* 17:14:08 rehrar: Sorry, stepped out for a bit, would prefer if you could run it 17:14:11 should we send an email on monero-announce mailing list? 17:14:12 Hi 17:14:16 it's being auto run dEBRUYNE 17:14:30 selsta: definitely, yes 17:14:50 AFAIK we only announced hard forks + security issues in the past 17:15:07 i'll make the blog post too. Would be good to have it out together with the release 17:15:24 Well, but we do want as many people as possible on this release, to get Dandelion++ working as well as possible, right? 17:15:31 i think it worth to send emails also for major releases. Such this one 17:15:56 yeah, especially if we want nodes to run dandelion 17:16:26 I think we also send out an email for the 0.14.1.0 major release 17:16:36 So wouldn't be out of place to send one now with the v0.16 release 17:16:49 ok 17:16:51 Definitely. 17:17:12 See what other coins announce to high heavens ... 17:18:45 anything else to discuss? 17:19:25 seems nay 17:20:51 rehrar: apparently CLSAG audit will be finished mid june 17:20:59 then we can plan the next hardfork 17:21:48 imo we should make it ASAP once it's done. Think of the savings. 17:22:10 ASAP = release 1 month before hf like last time 17:23:04 I meant plan hf pretty soon after it's done 17:23:10 yep 17:23:21 I know exchanges and stuff need time, and need to make sure trezor and ledger are good to go 17:23:26 August hard fork may work I guess 17:23:28 Maybe even July 17:23:32 ye 17:23:41 release in july, hf in august 17:24:08 Sounds like a plan 17:24:53 sarang is there any update on the audit? 17:25:05 we were waiting for a scope and price, correct? 17:25:11 or whatever it's called 17:26:17 last I heard, statement of work was done 17:26:58 then let's put up the proposal! woohoo! 17:27:25 rehrar: i think the audit workgroup is already working on it 17:27:28 hmm, maybe that was wrong. sarang last said in -research-lab that he has a call scheduled wit hauditors to discuss scope of work 17:27:55 with work to be performed mid-JUne 17:28:02 hyc: that is correct 17:28:26 I've been in contact with ledger and trezor folks to coordinate as well 17:28:40 To ensure that there's hardware device support 18:11:10 6553