Any interest in a dev meeting this sunday to discuss the upcoming v0.15.1.0 release?

Is there a release date for v0.15.1.0 already?

It's already quite some time since the last meeting, for whatever reason, so ...

normo: No specific date, we're just getting ready to branch

Thanks.

Thereafter it will be some time testing before a tag is set

Ok for the meeting. I would also go back to dev meetings every two weeks. I'm not sure of why we started to not having them anymore, but i think keeping a schedule it's good, especially in these times of low activity

^ From ErCiccione

Matrix doing its thing again

luigi1111w: CLI requires #6506 and #6510 and then we can branch

k

everyone ready for da branch?

I think yes, if something is missing we can PR it to branch

Thoughts on using 0.16 instead of 0.15.1 for the release?

It will probably incentivize people more to upgrade

It's not based on the 0.15 branch, so 0.16 makes more sense. But then the patch uses 0.15.1, so...

moneromooo: I can change the patch

I don’t really care

v0.16 will mean more updates

luigi1111w: would you prefer v0.16 or v0.15.1 ?

we're not on v15 network right?

so that association isn't exact

If you mean which protocol version, it's 12 currently.

right I was talking about major = fork

but anyway

more than that, though, I'd like to see a preliminary change list to judge if this is a "major" release, I guess

Dandelion (I think it's all in now ?)

major because all these new changes and features or minor because minor

luigi1111w: 519 commits since last release

including merge commits

txpool syncing.

bulletproofs speed improvements

Fairly large network bandwidth improvements.

luigi you wanted to not include the bp speed improvements yet but then you merged them so not sure if that was intentional

no I wanted to include them, just with a little more delay

ok

ideally more than a week or two between master merge and a new release

but "it should be fine"

will probably end up closer to a month I guess

I planned for 1 week of testing or so

fluffy has to fix dns....

with no fork we should be able to do what we want

dandelion sounds major ish

the other stuff not as much

(so far)

15.1 is already more than minor and less than major heh

but our branching is based on full numbers, so 16 makes more sense

yea I didn’t realize that v0.15.1 is also part of v0.15 branch

are there any incompatible changes?

und merging master into v0.15 branch sounds bad

yeah I won't do that, would make a 15.1 branch if we go that route

scoobybejesus: I think wallet cache is not compatible

but no network incompatibility

All the rest seems to be minor fixes really.

any incompatibilities like wallet cache skew to 16 for me, and dandelion

but having a "wow major release" that doesn't change much is a bit anticlimactic

The wallet cache should stil be compatible AFAIK.

in one sense, it could be seen as a major release because there's a lot of new stuff that could break

well, improved optimized etc

though i guess its more a matter of compatibility

it could be a major minor release

"Please upgrade, there's a lot of new stuff that could break"

lol

if I open a wallet with master and then again with v0.15.0.5 it rescans

something like this with made up numbers: if there are 30+ lines of nontrivial changes and 5+ substantial ones, then v16; if it's more like 15 and 2, then not

obviously not hard #s

Error: failed to load wallet: std::bad_alloc

^ when opening with master and then with v0.15.0.5 again

Then don't. It's not meant to do that.

Always go forward in versions.

(lines of changes for the release notes, not LoC obviously)

How about... 0.15.5.0.0 ? 15.5 is betwen 15 and 16.

and to think I was going to suggest that :D

0.15.half

I saved you the embarrassment :D

v1.0.0.0

dandelion = finally out of beta

So, it turns out my work branch db is incompatible with master. I might have a major patch somewhere I forgot to PR. Must be a while back, I don't remember doing db changes in a while...

we still have time before release

Oh I was not going to look right now. And if it changes db format, I won't PR it now.

ok

Ah, I store spend height with key images now. Helpful for wallet reorgs IIRC. Forgot all about this.

That wouldn't be major anyway.

Selecting a random p2p port on startup. Is that useful ? It's a WIP patch so not ready to go in.

Hah. The CLSAG patch. I wish.

-__-

Try #monero-pools

i am there also

Should we sign up for Github code scanning? Seems to be some kind of static analyzer..

Link to info?

If it does not had conditions etc, worth a try I guess.

no conditions, but it is beta so with waiting list

First page says "contact sales", so that looks like a condition :)

> semantic code analysis engine

luigi has to signup here github.com/features/security/advanced-security/signup

Might be neat to try, if it doesn't unnecessarily break any development workflows

I guess worst case we can turn it off again if it is too annoying or not helpful

luigi1111w: could you signup monero-project here? github.com/features/security/advanced-security/signup

You’re in the queue for the beta—we’ll let you know as soon as you have access.

ty