jesper.holck--- via Mailman-users writes:
I am a happy user running Mailman 3, dockerized, in combination with Mailcow. After a few initial problems, everything is running smoothly. Now I'm considering upgrading from 0.4 to 0.5.1, but I'm not sure about the right procedure. Is it something like this?
Evidently "0.4" and "0.5.1" refer to Mailcow, not Mailman. As usual, your first line of support for a third party integration should be the packager. We don't know what they're distributing. They have never consulted or informed us (which is perfectly reasonable for various reasons, but it does mean we can't be much help without a lot of work on our part which they have already done). Most issues in Mailman upgrades are in fact integration issues (eg, a dependency makes a change to its API and the first we know about it is when somebody tries to use the new release of the dependency in a Mailman install, or a stale patch by the integrator).
Assuming that they are distributing vanilla (straight from PyPI or git) versions of the Mailman suite and its dependencies (seems very likely), then I would guess your procedure should work. The database schema migrations should be automated in the docker compose phase. Issues are rare in Mailman suite upgrades, so unless you have space mission levels of need for uptime and reliability, I would just do it and deal with the fallout in the rare case.
If you are using the containerized Mailman provided by Abhilash, I don't know anything about it, and I'm not sure Mark knows much. So for issues with that particular product, you should probably CC him as he hasn't been active on the lists for months.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan