Monero Dev Meeting Note Highlights – 2019-03-10
Logs
351 lines
hycding
rbrunnerdong
rehraroyo
moneromoooThe witch.
rehrar1. Greetings
el00ruobuob_[m]Hi guys!
ArticMinehi
endogenicsup y'all
rbrunnerHi
ErCiccione[m]Hi
rehrar2. Fork Discussions
rehrarIs there anything that anyone present would like to discuss regarding the previous fork? We'll get to next point release items soon.
hyclooks like all quiet
rehrarit all went smooth as a baby's skin
rehrarYay. It looks like this meeting will be short indeed.
rbrunnerJust the first block was a real cliffhanger, right?
el00ruobuob_[m]it's been a long first block, besides that all's fine
ErCiccione[m]I take advantage of the quietness to say that i hope we will introduce a strict(er) release cycle for next release
sarangAt some point the goal is to move to a longer cycle, no?
hycmaybe we should focus on making reproducible builds work
ErCiccione[m]i recently took a look at how nextcloud does, they release every 4 months, so it's somehow usable for us
ErCiccione[m]hyc: solid +1 for that
ErCiccione[m]sarang: i hope so, afaik we never really had a proper discussion about that
sarangAs long as PoW tweaks are in the cards, I presume we'll stick to 6 months though
WoomyZoomyWhy the use of "goto" in bulletproof_PROVE instead of more common flow controls?
sarangthat's a question for moneromooo
moneromoooAh, simplicity.
rehrar3. Upcoming point release discussions
ErCiccione[m]sarang: sure, i was just pointing out that the timing is similar, so we could look at their system for inspiration. I can't find the page right now, but it was very solid, with planty of time for development, freeze and RC releases
moneromoooThey presumably don't have to have misc other software update in sync.
WoomyZoomyThanks
rehrarI know I had some questions, and the community at large is a little confused what is coming in the next point release, and if we have a timeline for that or not
moneromoooEverything that's on master, probably all/most of what's currnetly PRed and that's not super old.
moneromoooExcept maybe the 128 bit diff change.
hyccurrent master crashes
moneromoooWell, nohting says we can't add *more* fixes :)
ErCiccione[m](nextcloud's release schedule: https://docs.nextcloud.com/server/stable/admin_manual/release_schedule.html)
rehrarbecause I know some features people are excited about (like Trezor, no?) are coming out with that?
rehrarwe just going with "soon"?
sarangBetter faster stronger bulletproofs :D
el00ruobuob_[m]not too soon, we need a proper code freeze for this point release
ErCiccione[m]I would love to just have that week of freeze for the GUI this time
el00ruobuob_[m]yeah me too
moneromoooDid the GUI not choose to do a full release already ?
rbrunnerShould be easier now, with the threat of ASIC domination gone
hycyeah, it would be simpler if it was only the monero project. but we have to coordinate with exchanges/mining pools/3rd party miner developers/ etc
rbrunnerI think so, GUI was fully released
ErCiccione[m]moneromooo: yes, but would be good to have always that week for every release. I really need it to sync translations
sarangIs the intention to have new output selection for the point release?
moneromoooIf you and suraeNoether are happy with the details, sure.
sarangIt would be nice to have a rough deadline for freeze set
sarang(and we can discuss output selection at tomorrow's MRL meeting 17:00 UTC)
rehrarunfortunately hard to do without core?
rbrunnerMaybe also depends on when master will be able to work with the 3 Monero nets again, because basically testing can start only then
rehrarAlright, was there any other meeting items that someone wanted to discuss?
rehrarnow that we at the other side?
rbrunnerThe second hardfork will hardly give any problems, being rather trivial, right?
moneromoooLikely.
sarangIf this is a good avenue for it, I'd like any opinions on output selection since it is likely to change at the next point release (non consensus, of course)
sarangWe've discussed in MRL at length
pigeonsoh the point release will be a hardfork also?
rbrunnerNo, I mean the second hardfork in what, 2 hours or so?
pigeonswhen was the first?
moneromoooYesterday.
rbrunnerer .. yesterday
el00ruobuob_[m]most likely 22h rbrunner
pigeonsok i see i thought i was reading things wrong
rbrunnerAh, ok, 2 days
hycmore than 2 days, at the current rate
ArticMine0.9 days based upon 2 min blocks
ArticMineWe are more like 15 in blocks now
ArticMine15min
rbrunnerBut with nicely falling difficulty
moneromoooIf someone can get the master daemon to crash in debug mode with log level 2 and a core, that'd be great :)
rehrardoes anyone have any comments for sarang?
moneromoooBecause mine ain't.
el00ruobuob_[m]is it the output selection about coinbase transactions highlight by sgp_ ?
hyctook quite a while for my debug build to crash but it eventually did. before I removed the ssl patches
sarangel00ruobuob_[m]: it will help to address that, but in a more general sense
moneromoooDid you have a better stack trace, and logs showing what was being done in other threads ?
sarangwhere output selection is poorly weighted by block "density"
hycmoneromooo: I gave you the stack trace, didn't check other threads unfortunately. I can try spinning that up again.
el00ruobuob_[m]i have to confess i don't understand very well this subject sarang
moneromoooLogs will help here.
rehrarsarang, maybe discuss tomorrow at the MRL meeting
moneromoooIf another thread deleted some object, it might not show up on the stack trace if it's already done.
rehrarI think we can end here and business as usual can commence if that's alright with everyone.
rehrarNext weeks is community meeting, and we want to be desynced from them, so next meeting two weeks?
hycrehrar: sounds good
rehrarthanks for coming, and everyone was here with the new time (stupid DST)
rbrunnerOver here in Europe we will soon stop that DST nonsense
el00ruobuob_[m]thank you all!
rbrunnerMaybe last change next year
rbrunnerLikewise!
Sources and notes
- Meeting log: Overview and Logs for the Dev Meeting Held on 2019-03-10, getmonero.org. The official post carried the raw log and pointed readers to Hello Monero for the overview.
- Original Hello Monero URL slug recovered from the Wayback Machine index; the original page content did not survive, so this reconstruction carries the log as archived by the Monero Project.