05:15:44 <jeffro256> Idea for next release: re-branch from master and build with GUIX to soft launch the new build system before FCMP++. So far, AFAIK the stressnet hasn't identified any GUIX-specific bugs with the binaries, but it may happen with the wider audience of mainnet 
05:16:53 <jeffro256> I also don't want to try to fight new build issues and pre-fork FCMP++ integration issues at the same time if we can help it 
05:18:34 <jeffro256> That's not to mention tx relay v2, master<->release-v0.18 discrepcancies, and RandomX v2 integration if applicable 
08:24:17 <tobtoht> jeffro256: +1
08:24:24 <tobtoht> are we calling this branch release-v0.19 or ?
08:30:32 <tobtoht> so fcmp++ will be release-v0.20
09:54:06 <sech1> A reminder that it can't have consensus changes or it would have to be a hardfork
15:29:52 <selsta> this does not seem possible timing wise for the next release, but we can do a release branched from master before FCMP++
15:33:24 <selsta> .merge+ 10647
15:33:24 <xmr-pr> Added
16:40:04 <br-m> <jpk68:matrix.org> Apologies for being out of the loop - does this mean FCMP++ code will be added halfway through v0.19? Or that v0.19 is temporary and hardfork code will be in v0.20?
16:41:27 <br-m> <ofrnxmr:xmr.mx> The latter
16:42:36 <br-m> <ofrnxmr:xmr.mx> v0.19 will branch from master -> release-v0.19, where it will then become bug fixes etc.
16:42:36 <br-m> <ofrnxmr:xmr.mx> master will receive new features and fcmp code, and will be branched to v0.20 later
16:44:23 <br-m> <jpk68:matrix.org> How is the release name decided? Someone just suggests it?
16:44:44 <br-m> <jpk68:matrix.org> I know about the NAMING.md thing
16:44:47 <br-m> <ofrnxmr:xmr.mx> like fermi? 
16:45:49 <br-m> <ofrnxmr:xmr.mx> we should call it gattling gun 😆
16:46:33 <br-m> <jpk68:matrix.org> How about Praseodymium Wild Duck Cluster
16:46:41 <br-m> <jpk68:matrix.org> That has a certain ring to it
17:16:11 <nioc> v0.19 = neon (Ne) N_______   v0.20 = Sodium (Na) N__________
17:17:33 <nioc> or is name change just for hardforks? 
17:18:19 <br-m> <jpk68:matrix.org> I could be wrong, but it looks like it's for releases: https://github.com/monero-project/meta/blob/master/NAMING.md
17:18:47 <br-m> <jpk68:matrix.org> Also, v0.20 seems to be the first release where the element symbol doesn't start with the same letter as the English name
17:20:25 <br-m> <jpk68:matrix.org> That would kind of break the naming convention if that's what we have to stick with :(
17:21:26 <nioc> once before it didn't match because of a special case where we were looking for a W which is tungsten 
17:21:46 <nioc> so we also went out of order 
17:22:07 <nioc> honoring a dev that passed away 
17:38:08 <selsta> v0.15 Carbon Chamaeleon to v0.16 Nitrogen Nebula was without HF
17:40:45 <br-m> <syntheticbird> selsta: yeah but that was only justified because the name was much better
17:40:55 <br-m> <syntheticbird> so we need a better name
17:43:21 <br-m> <jpk68:matrix.org> Neon Nautilus?
17:44:35 <br-m> <syntheticbird> Nautilus a copyrighted by the GNOME foundation and anymore attempt at claiming it will be considered harassement towards the FOSS community.
17:45:30 <br-m> <syntheticbird> jk, sounds good
17:53:45 <nioc> needs to be an astronomical name
17:54:09 <br-m> <jpk68:matrix.org> It is, and it's also on the list
17:54:22 <br-m> <jpk68:matrix.org> (NAMING.md)
17:59:38 <br-m> <jpk68:matrix.org> Sodium Sputnik would be awesome
18:01:19 <jeffro256> Neon Nyx? https://en.wikipedia.org/wiki/Nyx_stream
18:19:43 <selsta> .merge+ 10637 10638
18:19:43 <xmr-pr> Added
18:53:20 <br-m> <jpk68:matrix.org> tobtoht: For 10685, would it maybe be better to use #if defined(__has_include) && __has_include(<unistd.h>)?
18:53:59 <br-m> <jpk68:matrix.org> This is C++17 (which we use AFAIK)
18:57:49 <br-m> <ofrnxmr:xmr.mx> @jpk68:matrix.org: Only on master
19:01:27 <nioc> Nyx sounds neat 
19:33:26 <br-m> <r4v3r23> nah nigga > <@jpk68:matrix.org> Neon Nautilus?
19:39:44 <selsta> current to-do list for v0.19 branch https://github.com/monero-project/monero/issues/10682
19:49:12 <br-m> <r4v3r23> selsta: polyseed, assuming @rbrunner7:monero.social finishes up the PR in time
19:53:00 <br-m> <r4v3r23> its been live for almost 4 years starting with feather, and used on virtually all mobile wallets
19:53:23 <br-m> <r4v3r23> i think its time to be officially added to the codebase
19:54:02 <br-m> <ofrnxmr:xmr.mx> Well, will need a pr before it can be finished
19:54:28 <br-m> <r4v3r23> is there a deadline?
19:54:39 <br-m> <ofrnxmr:xmr.mx> And there are multiple implementations w/ differing behavior (which is part of what rbrunner is trying to solve)
19:54:49 <br-m> <ofrnxmr:xmr.mx> @r4v3r23: The date for fork isnt set
19:55:02 <br-m> <r4v3r23> v0.19 is hard fork?
19:55:18 <br-m> <ofrnxmr:xmr.mx> not atm
19:55:30 <br-m> <ofrnxmr:xmr.mx> Could be if we ship randomx
19:55:41 <br-m> <r4v3r23> oh you mean branch
19:55:57 <br-m> <r4v3r23> so clearly theres time until a release
19:56:08 <br-m> <r4v3r23> polyseed PR was like 70% done IIRC
19:58:59 <br-m> <ofrnxmr:xmr.mx> Theres is no pr :P 
19:59:58 <br-m> <ofrnxmr:xmr.mx> @r4v3r23: i mean, whether we plan to include randomx changes is yet to be discussed. If we do, then yes, it would be a hard fork
20:00:18 <br-m> <ofrnxmr:xmr.mx> ^ > <jeffro256> That's not to mention tx relay v2, master<->release-v0.18 discrepcancies, and RandomX v2 integration if applicable
20:01:35 <br-m> <r4v3r23> @ofrnxmr:xmr.mx: the original question was is there a deadline for features to make it into v0.19 branch
20:03:15 <br-m> <ofrnxmr> Ideally there is just one more v18 release before the v19 branch, so. Probably a month or two? The deadline is whenever the following release is ready
20:05:46 <br-m> <r4v3r23> major version release should have at least 1 big feature
20:06:26 <br-m> <r4v3r23> lets see what rbrunners ETA is for polyseed
20:08:56 <br-m> <ofrnxmr:xmr.mx> @r4v3r23: It has like 4 years of features
20:10:04 <br-m> <r4v3r23> @ofrnxmr:xmr.mx: like what
20:10:14 <br-m> <r4v3r23> nice, selsta added polyseed
21:06:54 <tobtoht> .merges
21:06:54 <xmr-pr> 10512 10531 10533 10543 10637 10638 10647