- Mark Sapiro (mark@msapiro.net) [220315 22:18]:
On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote:
yes. the *current* template. but not the template that came with mailman3 3.2.1
Which is over 3 years old.
You should really be taking up these issues with Debian. Maybe if they got enough pressure from users, they would update their package.
Debian (as all distributions) freezes their packages when releasing, that's why it's called stable. If someone wants newer packages, it's possible to use stable-backports (see below).
Debian oldstable has mailman3 version 3.2.1. Debian stable has mailman3 version 3.3.1.
So, in this case, the version in Debian oldstable is used. Which is, well, a bit behind stable, because oldstable is one release behind from the current stable.
From (any) software point of view, distributions are always too old. However, having a frozen version of packages has great benefits for admins and reduces efforts. That's why distributions exists.
As I said multiple times (also here), my recommendation is: if the software in the distribution works for you, use it. If not, use your own. However, don't assume that pressure works here at all - distributions are freezing packages for very good reason.
As Debian is an volunteer effort, however it is always possible to help the distribution and get what you want by that.
A good way is stable-backports, because this allows the admin to select to have single packages from the more current testing branch of Debian. However, this only happens if someone does the necessary handholding. So far nobody volunteered for mailman, therefor mailman isn't in stable-backports. If I'd like to have a current mailman on Debian, that would be my path forward (together with running Debian stable, not oldstable); but that's not an easy one if you are not involved with debian yet.
Andi