From e33ac194e778d571c688636d472f65d6bda372f0 Mon Sep 17 00:00:00 2001 From: el00ruobuob Date: Sun, 10 Mar 2019 20:09:23 +0100 Subject: [PATCH] Logs from 2019-03-10 dev meeting + date correction on 02-11 dev meeting --- ...-for-the-dev-meeting-held-on-2018-02-11.md | 2 +- ...-for-the-dev-meeting-held-on-2019-03-10.md | 104 ++++++++++++++++++ 2 files changed, 105 insertions(+), 1 deletion(-) create mode 100644 _posts/2019-03-10-logs-for-the-dev-meeting-held-on-2019-03-10.md diff --git a/_posts/2018-02-11-logs-for-the-dev-meeting-held-on-2018-02-11.md b/_posts/2018-02-11-logs-for-the-dev-meeting-held-on-2018-02-11.md index 39a8fbf0..f21dee0f 100644 --- a/_posts/2018-02-11-logs-for-the-dev-meeting-held-on-2018-02-11.md +++ b/_posts/2018-02-11-logs-for-the-dev-meeting-held-on-2018-02-11.md @@ -1,6 +1,6 @@ --- layout: post -title: Overview and Logs for the Dev Meeting Held on 2018-01-28 +title: Overview and Logs for the Dev Meeting Held on 2018-02-11 summary: Discussion of open PRs and issues, Bulletproofs and auditing, March HF, slight PoW tweak, dedicated Monero hardware wallet, and miscellaneous tags: [dev diaries, core, crypto] author: dEBRUYNE / fluffypony diff --git a/_posts/2019-03-10-logs-for-the-dev-meeting-held-on-2019-03-10.md b/_posts/2019-03-10-logs-for-the-dev-meeting-held-on-2019-03-10.md new file mode 100644 index 00000000..014bc4a6 --- /dev/null +++ b/_posts/2019-03-10-logs-for-the-dev-meeting-held-on-2019-03-10.md @@ -0,0 +1,104 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2019-03-10 +summary: March 9th HF feedback, Point release discussions, and miscellaneous +tags: [dev diaries, core, crypto] +author: el00ruobuob / rehrar +--- + +# Logs + +**\** ding +**\** dong +**\** oyo +**\** The witch. +**\** 1. Greetings +**\** Hi guys! +**\** hi +**\** sup y'all +**\** Hi +**\** Hi +**\** 2. Fork Discussions +**\** Is there anything that anyone present would like to discuss regarding the previous fork? We'll get to next point release items soon. +**\** looks like all quiet +**\** it all went smooth as a baby's skin +**\** Yay. It looks like this meeting will be short indeed. +**\** Just the first block was a real cliffhanger, right? +**\** it's been a long first block, besides that all's fine +**\** I take advantage of the quietness to say that i hope we will introduce a strict(er) release cycle for next release +**\** At some point the goal is to move to a longer cycle, no? +**\** maybe we should focus on making reproducible builds work +**\** i recently took a look at how nextcloud does, they release every 4 months, so it's somehow usable for us +**\** hyc: solid +1 for that +**\** sarang: i hope so, afaik we never really had a proper discussion about that +**\** As long as PoW tweaks are in the cards, I presume we'll stick to 6 months though +**\** Why the use of "goto" in bulletproof\_PROVE instead of more common flow controls? +**\** that's a question for moneromooo +**\** Ah, simplicity. +**\** 3. Upcoming point release discussions +**\** 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 +**\** They presumably don't have to have misc other software update in sync. +**\** Thanks +**\** I 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 +**\** Everything that's on master, probably all/most of what's currnetly PRed and that's not super old. +**\** Except maybe the 128 bit diff change. +**\** \* current master crashes +**\** Well, nohting says we can't add \*more\* fixes :) +**\** (nextcloud's release schedule: https://docs.nextcloud.com/server/stable/admin\_manual/release\_schedule.html) +**\** because I know some features people are excited about (like Trezor, no?) are coming out with that? +**\** we just going with "soon"? +**\** Better faster stronger bulletproofs :D +**\** not too soon, we need a proper code freeze for this point release +**\** I would love to just have that week of freeze for the GUI this time +**\** yeah me too +**\** Did the GUI not choose to do a full release already ? +**\** Should be easier now, with the threat of ASIC domination gone +**\** yeah, 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 +**\** I think so, GUI was fully released +**\** moneromooo: yes, but would be good to have always that week for every release. I really need it to sync translations +**\** Is the intention to have new output selection for the point release? +**\** If you and suraeNoether are happy with the details, sure. +**\** It would be nice to have a rough deadline for freeze set +**\** (and we can discuss output selection at tomorrow's MRL meeting 17:00 UTC) +**\** unfortunately hard to do without core? +**\** Maybe also depends on when master will be able to work with the 3 Monero nets again, because basically testing can start only then +**\** Alright, was there any other meeting items that someone wanted to discuss? +**\** now that we at the other side? +**\** The second hardfork will hardly give any problems, being rather trivial, right? +**\** Likely. +**\** If 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) +**\** We've discussed in MRL at length +**\** oh the point release will be a hardfork also? +**\** No, I mean the second hardfork in what, 2 hours or so? +**\** when was the first? +**\** Yesterday. +**\** er .. yesterday +**\** most likely 22h rbrunner +**\** ok i see i thought i was reading things wrong +**\** Ah, ok, 2 days +**\** more than 2 days, at the current rate +**\** 0.9 days based upon 2 min blocks +**\** We are more like 15 in blocks now +**\** 15min +**\** But with nicely falling difficulty +**\** If someone can get the master daemon to crash in debug mode with log level 2 and a core, that'd be great :) +**\** does anyone have any comments for sarang? +**\** Because mine ain't. +**\** is it the output selection about coinbase transactions highlight by sgp\_ ? +**\** took quite a while for my debug build to crash but it eventually did. before I removed the ssl patches +**\** el00ruobuob\_[m]: it will help to address that, but in a more general sense +**\** Did you have a better stack trace, and logs showing what was being done in other threads ? +**\** where output selection is poorly weighted by block "density" +**\** moneromooo: I gave you the stack trace, didn't check other threads unfortunately. I can try spinning that up again. +**\** i have to confess i don't understand very well this subject sarang +**\** Logs will help here. +**\** sarang, maybe discuss tomorrow at the MRL meeting +**\** If another thread deleted some object, it might not show up on the stack trace if it's already done. +**\** I think we can end here and business as usual can commence if that's alright with everyone. +**\** Next weeks is community meeting, and we want to be desynced from them, so next meeting two weeks? +**\** rehrar: sounds good +**\** thanks for coming, and everyone was here with the new time (stupid DST) +**\** Over here in Europe we will soon stop that DST nonsense +**\** thank you all! +**\** Maybe last change next year +**\** Likewise!