08:49:56 <dEBRUYNE> Any interest in a dev meeting this sunday to discuss the upcoming v0.15.1.0 release?
09:03:18 <normo> Is there a release date for v0.15.1.0 already?
09:03:49 <rbrunner> It's already quite some time since the last meeting, for whatever reason, so ...
09:04:12 <dEBRUYNE> normo: No specific date, we're just getting ready to branch
09:04:19 <normo> Thanks.
09:04:22 <dEBRUYNE> Thereafter it will be some time testing before a tag is set
10:24:09 <Guest55672> 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
10:24:25 <Guest55672> ^ From ErCiccione
10:24:37 <Guest55672> Matrix doing its thing again
15:32:15 <selsta> luigi1111w: CLI requires #6506 and #6510 and then we can branch
15:32:27 <luigi1111w> k
16:51:17 <luigi1111w> everyone ready for da branch?
17:05:38 <selsta> I think yes, if something is missing we can PR it to branch
17:48:05 <dEBRUYNE> Thoughts on using 0.16 instead of 0.15.1 for the release?
17:48:10 <dEBRUYNE> It will probably incentivize people more to upgrade
17:50:54 <moneromooo> It's not based on the 0.15 branch, so 0.16 makes more sense. But then the patch uses 0.15.1, so...
17:52:12 <selsta> moneromooo: I can change the patch
17:52:19 <selsta> I don’t really care
17:52:31 <selsta> v0.16 will mean more updates
17:55:41 <selsta> luigi1111w: would you prefer v0.16 or v0.15.1 ?
17:58:25 <luigi1111w> we're not on v15 network right?
17:58:31 <luigi1111w> so that association isn't exact
18:00:16 <moneromooo> If you mean which protocol version, it's 12 currently.
18:00:27 <luigi1111w> right I was talking about major = fork
18:00:31 <luigi1111w> but anyway
18:00:52 <luigi1111w> more than that, though, I'd like to see a preliminary change list to judge if this is a "major" release, I guess
18:01:16 <moneromooo> Dandelion (I think it's all in now ?)
18:01:17 <luigi1111w> major because all these new changes and features or minor because minor
18:03:47 <selsta> luigi1111w: 519 commits since last release
18:03:56 <selsta> including merge commits
18:04:01 <selsta> https://github.com/monero-project/monero/compare/v0.15.0.5...master
18:04:30 <moneromooo> txpool syncing.
18:05:44 <selsta> bulletproofs speed improvements
18:06:04 <moneromooo> Fairly large network bandwidth improvements.
18:06:39 <selsta> luigi you wanted to not include the bp speed improvements yet but then you merged them so not sure if that was intentional
18:06:54 <luigi1111w> no I wanted to include them, just with a little more delay
18:06:59 <selsta> ok
18:07:17 <luigi1111w> ideally more than a week or two between master merge and a new release
18:07:23 <luigi1111w> but "it should be fine"
18:07:33 <luigi1111w> will probably end up closer to a month I guess
18:07:34 <selsta> I planned for 1 week of testing or so
18:07:55 <selsta> fluffy has to fix dns....
18:08:01 <luigi1111w> with no fork we should be able to do what we want
18:08:17 <luigi1111w> dandelion sounds major ish
18:08:21 <luigi1111w> the other stuff not as much
18:08:23 <luigi1111w> (so far)
18:09:06 <luigi1111w> 15.1 is already more than minor and less than major heh
18:09:29 <luigi1111w> but our branching is based on full numbers, so 16 makes more sense
18:10:03 <selsta> yea I didn’t realize that v0.15.1 is also part of v0.15 branch
18:10:09 <scoobybejesus> are there any incompatible changes?
18:10:10 <selsta> und merging master into v0.15 branch sounds bad
18:10:46 <luigi1111w> yeah I won't do that, would make a 15.1 branch if we go that route
18:10:58 <selsta> scoobybejesus: I think wallet cache is not compatible
18:11:10 <selsta> but no network incompatibility
18:12:41 <moneromooo> All the rest seems to be minor fixes really.
18:13:37 <luigi1111w> any incompatibilities like wallet cache skew to 16 for me, and dandelion
18:13:57 <luigi1111w> but having a "wow major release" that doesn't change much is a bit anticlimactic
18:14:01 <moneromooo> The wallet cache should stil be compatible AFAIK.
18:14:51 <gingeropolous> in one sense, it could be seen as a major release because there's a lot of new stuff that could break
18:15:04 <gingeropolous> well, improved optimized etc
18:15:38 <gingeropolous> though i guess its more a matter of compatibility
18:15:56 <gingeropolous> it could be a major minor release
18:16:01 <moneromooo> "Please upgrade, there's a lot of new stuff that could break"
18:16:08 <gingeropolous> lol
18:16:23 <selsta> if I open a wallet with master and then again with v0.15.0.5 it rescans
18:16:49 <luigi1111w> 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
18:16:53 <luigi1111w> obviously not hard #s
18:16:54 <selsta> Error: failed to load wallet: std::bad_alloc
18:17:12 <selsta> ^ when opening with master and then with v0.15.0.5 again
18:17:24 <moneromooo> Then don't. It's not meant to do that.
18:17:34 <moneromooo> Always go forward in versions.
18:18:28 <luigi1111w> (lines of changes for the release notes, not LoC obviously)
18:18:48 <moneromooo> How about... 0.15.5.0.0 ? 15.5 is betwen 15 and 16.
18:18:53 * moneromooo grabs shield
18:19:31 <luigi1111w> and to think I was going to suggest that :D
18:19:41 <luigi1111w> 0.15.half
18:19:45 <moneromooo> I saved you the embarrassment :D
18:19:53 <selsta> v1.0.0.0
18:20:03 <selsta> dandelion = finally out of beta
18:21:04 <moneromooo> 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...
18:21:38 <selsta> we still have time before release
18:22:00 <moneromooo> Oh I was not going to look right now. And if it changes db format, I won't PR it now.
18:22:31 <selsta> ok
18:23:05 <moneromooo> Ah, I store spend height with key images now. Helpful for wallet reorgs IIRC. Forgot all about this.
18:23:42 <moneromooo> That wouldn't be major anyway.
18:27:19 <moneromooo> Selecting a random p2p port on startup. Is that useful ? It's a WIP patch so not ready to go in.
18:28:04 <moneromooo> Hah. The CLSAG patch. I wish.
18:28:10 <sarang> -__-
18:29:21 * moneromooo hands sarang the whisky bottle
18:30:42 * sarang accepts
19:12:54 * xmrpools anybody know how to create a mining pool ? i try many tutorials but doesnt start ..
19:15:25 <moneromooo> Try #monero-pools
19:15:26 * xmrpools anybody know how to create a mining pool ? i try many tutorials but doesnt start ..
19:15:52 <xmrpools> i am there also
21:50:50 <selsta> Should we sign up for Github code scanning? Seems to be some kind of static analyzer..
22:02:30 <sarang> Link to info?
22:02:42 <moneromooo> If it does not had conditions etc, worth a try I guess.
22:03:17 <selsta> https://github.com/features/security
22:03:40 <selsta> no conditions, but it is beta so with waiting list
22:04:21 <moneromooo> First page says "contact sales", so that looks like a condition :)
22:04:22 <selsta> > semantic code analysis engine
22:04:37 <selsta> luigi has to signup here https://github.com/features/security/advanced-security/signup
22:04:39 <sarang> Might be neat to try, if it doesn't unnecessarily break any development workflows
22:06:17 <selsta> I guess worst case we can turn it off again if it is too annoying or not helpful
22:07:46 <selsta> luigi1111w: could you signup monero-project here? https://github.com/features/security/advanced-security/signup
22:17:15 <luigi1111w> You’re in the queue for the beta—we’ll let you know as soon as you have access.
22:18:31 <selsta> ty