On Wed, Aug 14, 2019, at 10:08 AM, Stephen J. Turnbull wrote:
sandeep kumar writes:
Now that we are ready to go into production. We are currently running mailman 2 in our production. Now the biggest challenge is we have to migrate around 3000 lists from mailman 2 to mailman 3. Is there any documentation
There's a small amount, but we're not satisfied with it. We have an on-going Season of Docs project to create migration documentation.
or any inputs from the team would be appreciated and will be very helpful.
Abhilash and Mark have substantial experience with migrating lists, and operating Mailman 2 in parallel with Mailman 3 (ie, gradual migration, not the same list on both servers!) However, they've been doing this at scale of dozens of lists, maybe a dozen at a time.
I've also been (very slowly) working on automating the workflow for migration to a level that it requires minimal user intervention. This hasn't been tested or completed yet1.
It is mostly complete, but if you can help complete it, it should be a bit nicer than manually porting every list (i.e. multiple-commands per list right now) vs single command with exception handling to keep working till it reaches end. For 3k lists, it might be useful :)
I hope that some of our really large-scale users will have something to say, but the cases I'm aware of are at your stage more or less -- no post-mortems yet that I know of.
Iam trying to access docs.mailman3.org but it is not opening don't why.?
It appears that recent Firefox is very picky about the TLS versions it will connect to, and somehow mailman3.org doesn't support that. Abhilash?
DNS records need updating, I'm gonna poke at Barry.
In the meantime, try other browsers which may not be so picky about crypto algorithms. Also you can try mailman.readthedocs.io.
Steve
-- thanks, Abhilash Raj (maxking)