Ah, so more like release notes than a changelog. Sorry, I usually step onto landmines by being affected by uncommon issues in any software, kinda gotten used to it by now. That’s why I check the changes first, if I don’t find it under changes I assume it’s something with my setup, I thought it’d disappear with a restart or something, but I reported it just in case.
The code itself is too much for me to examine/observe changes. I do read the Github changelog though.
I had the automated updates enabled at the very start and immediately stepped onto a landmine, as usual. Whole node went down, which would’ve happened anyway, but the worst thing was it was in the middle of the night and I did not see it until well into the next day (this was a time when permitted downtime was still under question).
Since then I have never enabled it again. I tried updating as infrequently as possible, but then it looked like I was not getting nearly as much data as usual after I was 2 versions behind (still well within the minimal version), so then I changed it to updating more frequently, at random. But this time it seems I’ve updated too fast. I’ll try to wait at least a week or so usually, but, you know… OCD.
Most importantly, there still aren’t any instructions, nor a way to autostart/stop for my OS on documentation.storj.io, so I didn’t touch anything that I didn’t have to until an official way was published, so that’s mostly why it’s still disabled.
So, in essence, manual updates because I can choose when, random events are a catastrophe for me. Most convenient thing would be to have an “Update” button in the SNOboard.