I dunno, I’ve never found it all that onerous.

I have a couple of dozen (perhaps ~50) containers running across a bunch of servers, I read the release notes via RSS so I don’t go hunting for news of updates or need to remember to check, and I update when I’m ready to. Security updates will probably be applied right away (unless I’ve read the notes and decided it’s not critical for my deployment(s)), for feature updates I’ll usually wait a few days (dodged a few bullets that way over the years) or longer if I’m busy, and for major releases I’ll often wait until the first point release unless there’s something new I really want.

Unless there are breaking changes it takes a few moments to update the docker-compose.yaml and then dcp (aliased to docker compose pull) and dcdup (aliased to docker compose down && docker compose up -d && docker compose logs -f).

I probably do spend upwards of maybe 15 or 20 minutes a week under normal circumstances, but it’s really not a full time job for me 🤷.

I use digests in my docker compose files, and I update them when new versions are released (after reading the release notes) 🤷

My understanding was (perhaps wrong?) that the “Mattermost Team Edition” is offered under the AGPL, and then the “Enterprise” Editions (starting with the “Entry Edition”) have additional restrictions (including the 10k message limit in the “Entry Edition” that everyone’s been talking about). They do a good job of hiding the “Team Edition” (it’s almost like the don’t really want to have to offer an open-source editions… 🤔), but it is there if you can find it. https://docs.mattermost.com/product-overview/editions-and-offerings.html#mattermost-team-edition

I’ve been running self-hosted Mattermost for a medium-sized academic org for a while now, and upgrades have always been a breeze, tbh (but I only use the version with open-source code only – the “Team Edition” --, not the Entry or any of the other Enterprise Editions, so that may be relevant).