SebS
SebS You could as well argue “why release notes, they can as well just read the commits”. Just that there are release notes does not mean that you can’t also make it comfortable.
Yes, of course, there is always more that can be done to make things more convenient for the user. However, one must also weigh the costs against the benefits.
For example, to install automatically, you’d need to add checks for all possible distros and package managers. In general, I think it’s risky if a script just starts installing packages on the underlying OS. Mailcow doesn’t know how your system is configured or what state it’s in regarding system upgrades. What if there are dependency issues, or in the worst case, the package manager breaks your system? Sure, that’s rather unlikely in this specific case, but you can never be 100% certain. That’s probably why they decided against it. I’d say that’s better than putting in a huge amount of effort for a ‘sanitised’ script that still has the potential to break a user’s system just to save them from typing apt install jq.
I do agree though, they could have shown a better message. Something like: “Please install jq via your distro’s package manager, and restart the update script.”
SebS As for the other thing, I’m not a native speaker and seem to have mixed up intern and trainee, sorry.
Yeah, sorry, I may have misunderstood that, and gone a bit too far there. However, whether they’re interns, trainees, or regular employees, it just sounded to me like your staff needs to do everything 110% perfectly, otherwise they have a tough time. What you probably meant, though, is that your trainees could do a better job than the Mailcow developers.
Either way, in my humble opinion, your last sentence was somewhat unnecessary and inappropriate, especially over such a minor “issue,” ;-)