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

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

That's not to mention tx relay v2, master<->release-v0.18 discrepcancies, and RandomX v2 integration if applicable

jeffro256: +1

are we calling this branch release-v0.19 or ?

so fcmp++ will be release-v0.20

A reminder that it can't have consensus changes or it would have to be a hardfork

this does not seem possible timing wise for the next release, but we can do a release branched from master before FCMP++

.merge+ 10647

Added

<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?

<ofrnxmr:xmr.mx> The latter

<ofrnxmr:xmr.mx> v0.19 will branch from master -> release-v0.19, where it will then become bug fixes etc.

<ofrnxmr:xmr.mx> master will receive new features and fcmp code, and will be branched to v0.20 later

<jpk68:matrix.org> How is the release name decided? Someone just suggests it?

<jpk68:matrix.org> I know about the NAMING.md thing

<ofrnxmr:xmr.mx> like fermi?

<ofrnxmr:xmr.mx> we should call it gattling gun 😆

<jpk68:matrix.org> How about Praseodymium Wild Duck Cluster

<jpk68:matrix.org> That has a certain ring to it

v0.19 = neon (Ne) N_______ v0.20 = Sodium (Na) N__________

or is name change just for hardforks?

<jpk68:matrix.org> I could be wrong, but it looks like it's for releases: github.com/monero-project/meta/blob/master/NAMING.md

<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

<jpk68:matrix.org> That would kind of break the naming convention if that's what we have to stick with :(

once before it didn't match because of a special case where we were looking for a W which is tungsten

so we also went out of order

honoring a dev that passed away

v0.15 Carbon Chamaeleon to v0.16 Nitrogen Nebula was without HF

<syntheticbird> selsta: yeah but that was only justified because the name was much better

<syntheticbird> so we need a better name

<jpk68:matrix.org> Neon Nautilus?

<syntheticbird> Nautilus a copyrighted by the GNOME foundation and anymore attempt at claiming it will be considered harassement towards the FOSS community.

<syntheticbird> jk, sounds good

needs to be an astronomical name

<jpk68:matrix.org> It is, and it's also on the list

<jpk68:matrix.org> (NAMING.md)

<jpk68:matrix.org> Sodium Sputnik would be awesome

Neon Nyx? en.wikipedia.org/wiki/Nyx_stream

.merge+ 10637 10638

Added

<jpk68:matrix.org> tobtoht: For 10685, would it maybe be better to use #if defined(__has_include) && __has_include(<unistd.h>)?

<jpk68:matrix.org> This is C++17 (which we use AFAIK)

<ofrnxmr:xmr.mx> @jpk68:matrix.org: Only on master

Nyx sounds neat

<r4v3r23> nah nigga > <@jpk68:matrix.org> Neon Nautilus?

current to-do list for v0.19 branch monero-project/monero #10682

<r4v3r23> selsta: polyseed, assuming @rbrunner7:monero.social finishes up the PR in time

<r4v3r23> its been live for almost 4 years starting with feather, and used on virtually all mobile wallets

<r4v3r23> i think its time to be officially added to the codebase

<ofrnxmr:xmr.mx> Well, will need a pr before it can be finished

<r4v3r23> is there a deadline?

<ofrnxmr:xmr.mx> And there are multiple implementations w/ differing behavior (which is part of what rbrunner is trying to solve)

<ofrnxmr:xmr.mx> @r4v3r23: The date for fork isnt set

<r4v3r23> v0.19 is hard fork?

<ofrnxmr:xmr.mx> not atm

<ofrnxmr:xmr.mx> Could be if we ship randomx

<r4v3r23> oh you mean branch

<r4v3r23> so clearly theres time until a release

<r4v3r23> polyseed PR was like 70% done IIRC

<ofrnxmr:xmr.mx> Theres is no pr :P

<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

<ofrnxmr:xmr.mx> ^ > <jeffro256> That's not to mention tx relay v2, master<->release-v0.18 discrepcancies, and RandomX v2 integration if applicable

<r4v3r23> @ofrnxmr:xmr.mx: the original question was is there a deadline for features to make it into v0.19 branch

<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

<r4v3r23> major version release should have at least 1 big feature

<r4v3r23> lets see what rbrunners ETA is for polyseed

<ofrnxmr:xmr.mx> @r4v3r23: It has like 4 years of features

<r4v3r23> @ofrnxmr:xmr.mx: like what

<r4v3r23> nice, selsta added polyseed

.merges

10512 10531 10533 10543 10637 10638 10647