--- layout: post title: Overview and Logs for the Dev Meeting Held on 2019-10-20 summary: Development status, 0.15 release discussion, Network upgrade naming, and miscellaneous tags: [dev diaries, core, crypto] author: el00ruobuob / rehrar --- # Logs **\** Alright everyone. 17 UTC. **\** Meeting time. **\** 1. Greetings **\** hey **\** Hi **\** \\o/ **\** small crowd today? **\** hi **\** well, perhaps people will trickle in. **\** Two weeks ago I was at HCPP, so I wasn't able to be here for a meeting. Was there one? **\** I am here **\** No, neither 1 week ago **\** I think we decided to postpone it **\** ok, so **\** 2. What's been completed since the previous meeting (a month ago) **\** a lot of PRs got merged **\** has the v12 forkheight been merged? **\** You can now sync off pruned nodes. **\** Not yet. **\** I think that will probably be on the last merge list before we branch **\** ^ rehrar **\** vtnerd\_\_: do you intend your latest network changes to go in for the fork ? **\** the one that is up for review, yes that would be the hope (provided its determined to be ready) **\** its not needed for the hardfork, so if you feel it should wait, then my recommendation would be to wait for a point release **\** the problem is that re-testing some of your recommendations are likely to take up time before the upcoming branch, but I will try **\** I think that and pay-for-service are the only large ones left. **\** Oh, and the defer tx verification one. Not huge either but a bit substantial. **\** are either of those expected to be in? **\** Hopefully all of them. **\** pay-for-service goes next, I've kept it waiting for long enough. **\** sounds good **\** Did I get that right that a PR is waiting in that batch that will cause testnet to reorg back to some much earlier blockheight? **\** not that I've seen **\** ? **\** Maybe I misunderstood then, while reading something up here **\** I said so, but I was wrong. The rules are different, but actually coincide in practice. **\** Surprising **\** All the better **\** They'll stop conciding whe nthe block size shoots up. **\** So we only need some seed nodes working for testnet ... caugh ... caugh **\** gingeropolous added one, that'll be merged soon. **\** Nice **\** dEBRUYNE: didn't you get hold of fluffypony regarding seed nodes? **\** He posted an update here 1-2 days ago **\ \** re: testnet nodes, I've been having some issues with the boxes I run, but there are other people running testnet nodes besides me **\** ah, I missed that. ok **\** Especially nice that stagenet gets a third seed node, with the only two so far probably just sitting side-by-side and offering zero redundancy **\** well, not zero, but you get what I mean ... **\** Anything else of note to discuss on what's been done this past month? **\** sounds like not **\** Alrighty. **\** 3. Fork related things **\** is there anything that is needed, desired, wanted, or otherwise needs to be discussed regarding the upcoming fork. **\** FYI, there will be probably RandomX 1.1.5 with some OpenBSD-related fixes **\** but best if 1.1.4 is merged first (1.1.5 doesn't need any changes in monero code) **\** that's PR#5980 for v1.1.4 **\** yes **\** ok, no other fork related topics? If not we can move on. **\** Zipping through this meeting. **\** is anyone from GUI here? dsc\_ selsta **\** yes we only had bug fixes recently **\** GUI is ready for v0.15 **\** ok **\** 4. Any Ticket/PR related questions? **\** By the way, is there already a final name for the release? I could use it for adjusting the Windows installer. Is it now crab something? **\** carbon crab? **\** I don't recall a final name decision **\** Yeah, that one **\** Where was the discussion? **\** Me neither, that's why I ask for sure **\** We can make a decision here. **\** I think there was some chatter in a Reddit thread once **\** I think some names got tossed around in this channel a few weeks ago. but nothing decided. **\** camelopardalis is satifyingly complicated. **\** you guys want to decide now? Or not urgent? **\** oh yeah, that was my suggestion **\** I think pony likes to leave it for a reddit vote where people can't break things **\** we can do it now, there seems to be enough people present **\** ah **\** Pony usually makes a Github thread and links that to reddit iirc **\** I would also prefer a Reddit thread, more fun for the fans, so to say **\** (re: name) **\** But why not soon, e.g. tomorrow **\** does the 24th Oct code freeze still apply? **\** (it should) **\** there was a mention of name on reddit https://www.reddit.com/r/Monero/comments/d884zt/preliminary\_information\_thread\_regarding\_the/f2zfmr1/ **\** but pretty sure that was just relaying a suggestion from here on IRC **\** I can make a meta issue and link to it on the Reddit **\** cool **\** Yeah that was me, but I forgot where I got that Carbon Crab **\** Yes, do go ahead **\** rehrar: should I ask pony first if he wants to uphold the tradition? **\** (I have the previous discussion in chat logs, was in this channel a couple weeks ago) **\** Callisto alliterates nicely too fwiw. **\** sure **\** Hmm, yes indeed **\** "Crab" is very short **\** Is there anything else to discuss besides the naming? **\** Kind of a free for all time. **\** that's always the hardest problem in computing... **\** So it looks surprisingly good for this code-freeze **\** it's because we extended it out an extra month? **\** Alright, well if there's nothing else to discuss, then we can go ahead and break. Doughnuts are on the table on your way out.