On Jun 20, 2016, at 10:47 PM, Bill wrote:
And it leads me to think about timelines.
I'm aware that the freeze for Debian 9 (Stretch) is scheduled for the end of this year, and that we can expect it to be released sometime in mid-2017. (Don't quote me on that though ;) And I'm not sure about Centos, I didn't see a Mailman 3.0 package there or in Fedora.
We have a Debian maintainer who did some work on packaging, but got stuck on a few issues. I think one of the biggest problems is also something that HK/Postorius is grappling with right now - the eminent demise of persona.org. Work is being done to switch over to django-social-auth, and that's a blocker for a full 3.1 suite release.
For the core, the last big missing thing is the unsubscription workflow (see GL#213). I'll be looking at that, trying to adapt or finish Abhilash's work there.
But is there any chance that a Mailman 3.0 or 3.1 package is going to make it into current release cycles?
I'd like for it to happen; we'll have to see.
But we're in the evaluation/design phase of this project and from the providers point of view it would be helpful to know if they should wait a few months for Mailman 3.0/3.1 or just go ahead now with 2.1.x and upgrade to 3.1 at some point down the road. While their list admins are experienced, they are new to Mailman and the fewer burps the better. Although they may very well take a run at 3.0 now and see how things work out. We just need some sort of timeline to consider.
I still think we can get a 3.1 release out by year's end, if not sooner. As I say, we have just a couple of blockers left, though they may or may not be small. I'd say, don't try to deploy 3.0, but either go with the git heads, or wait for hopefully some beta releases of 3.1 coming soon. I am seriously considering not releasing a 3.0.4 and just EOL'ing 3.0.x once 3.1 is released. It should be a smooth upgrade if you already have 3.0 deployed.
Cheers, -Barry