18:30:07 <sumpfralle2> #startmeeting
18:30:07 <MeetBot> Meeting started Wed Oct 16 18:30:07 2019 UTC.  The chair is sumpfralle2. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:30:07 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:30:26 <sumpfralle2> It is Wednesday again - time for our weekly IRC meeting!
18:30:40 <sumpfralle2> Who is around?
18:31:10 <TheSnide> hi
18:34:19 * h01ger not really
18:34:22 * h01ger waves
18:40:35 <sumpfralle2> Great!
18:41:05 <sumpfralle2> And I am sure, you were all silently working on making munin a more beautiful tool during the last week? :)
18:42:24 <sumpfralle2> I only managed to do a bit of reviewing of contributions.
18:43:11 <sumpfralle2> My attempt at running munin-run in a systemd-created environment (equivalent to munin-node) did not succeed, yet.
18:44:03 * h01ger only has this usual question: when will 2.0.50/2.999.15 be ready? release early release often is really good methology in my experience. after the release is before the release and all that
18:44:34 <sumpfralle2> you are nicely predictable :)
18:44:36 * h01ger is also sorry he has very little time for munin these days, happyly busy elsewhere, mostly in reproducible builds land..
18:44:50 <sumpfralle2> a good place to be and to go to!
18:44:53 <h01ger> :)
18:45:35 * TheSnide looks at the gitlog
18:46:13 <h01ger> i've also very briefly looked into hooking up munin with grafana recently. and while this was easy for one host, it didnt seem to be for many or a lot of hosts - this is were munin still shines brightly. setting up graphs (and simple monitoring too) for hundreds of systems? super easy.
18:47:34 <TheSnide> yeah. we shine to monitor the monitoring tools. And to ensure that they are really are of low overhead
18:48:47 <h01ger> :)
18:48:56 <TheSnide> https://github.com/munin-monitoring/munin/milestone/12 is rather ambitious.
18:49:20 <TheSnide> I'll try to merge those PR next week at least
18:49:51 <h01ger> what do you think about monthly releases of 2.0.x? its in low maintenance mode, isnt it? so the development focus and difficult changes should be in 2.999^w3.0, or?
18:50:06 <h01ger> so i would imagine a release is like 15min of work...
18:50:21 <h01ger> (a 2.0.x release)
18:50:24 <TheSnide> h01ger: it is.
18:50:30 <TheSnide> (15min)
18:50:36 <TheSnide> not even that said
18:50:37 <h01ger> inlc changelog writing?
18:50:48 <h01ger> or can that be automated from commits? ;)
18:51:07 <TheSnide> i automated that using `git shortlog` as I am super lazy
18:52:17 <TheSnide> On the bright side, demo.munin-monitoring.org has been untouched for quite a while now. As is still running nicely.
18:52:34 <TheSnide> so, that would vet for stability.
18:52:44 <h01ger> in 2019 2.0.45-49 were recently. so one release once every two months, almost. my idea with doing it bi-weekly was basically to release during the meeting. (with only changes from until then, anything to be discussed at the meeting by definition is nothing for an easy 2.0.x release)
18:52:45 <TheSnide> (of the 2.999.x branch)
18:52:56 <h01ger> call it 3.0? ;)
18:53:00 * h01ger runs
18:53:24 <TheSnide> well, there are still some crucial bugs
18:53:42 * h01ger nods
18:53:47 * TheSnide should kick himself and fix them
18:56:50 <sumpfralle2> I felt inspired and just tagged 2.0.50.
18:56:57 <sumpfralle2> TheSnide: feel free to upload it!
19:01:11 <TheSnide> http://downloads.munin-monitoring.org/munin/stable/2.0.50/
19:06:33 <TheSnide> #agreed 2.0.x releases will be done during the meeting on a bi-weekly basis.
19:07:28 <sumpfralle2> :)
19:08:21 <sumpfralle2> I guess, this is a good end for the meeting. Happy hacking!
19:08:24 <sumpfralle2> #endmeeting