Re: [Mailman-Developers] Migration script from MM2 to MM3
On Sep 20, 2013, at 12:46 PM, Aurelien Bompard wrote:
What do you think? Bad timing? Any existing work I'm missing?
I think it's a *great* idea.
No, perfect timing.
Not that I know of! :)
What we've said in the past is that we weren't going to promise conversion scripts from 2.1 to 3.0, partly because that work was incomplete, but also because we wanted to caution users not to just blindly upgrade as soon as 3.0 is released. But I think having a reliable, well-tested, non-destructive option to upgrade would be wonderful, especially because I fully hope that a site could run 2.1 and 3.0 together for a while.
Any help you need, let me know.
(I've been ridiculously swamped at work these past few weeks. Apologies for being rather quiet lately. I hope that'll improve in the next couple of weeks.)
Cheers, -Barry
On 21 Sep 2013, at 16:48, Barry Warsaw <barry@list.org> wrote:
On Sep 20, 2013, at 12:46 PM, Aurelien Bompard wrote:
What do you think? Bad timing? Any existing work I'm missing?
I think it's a *great* idea.
No, perfect timing.
Not that I know of! :)
What we've said in the past is that we weren't going to promise conversion scripts from 2.1 to 3.0, partly because that work was incomplete, but also because we wanted to caution users not to just blindly upgrade as soon as 3.0 is released. But I think having a reliable, well-tested, non-destructive option to upgrade would be wonderful, especially because I fully hope that a site could run 2.1 and 3.0 together for a while.
Presumably, with some lists on 2.1, and others on 3.0.
That would mean the admin would need to be able to specify which lists to migrate.
I guess you might want to consider whether special handling is needed for virtual domains. I know we’ve been operating a nasty cludge, where we’re using SUBDOMAIN_LISTNAME@DOMAIN for an internal representation of LISTNAME@SUBDOMAIN.DOMAIN. I suppose that’s unusual or unique, but it might be nice to allow migration of a list in 2.1 to a list with a new name in 3.0.
Any help you need, let me know.
(I've been ridiculously swamped at work these past few weeks. Apologies for being rather quiet lately. I hope that'll improve in the next couple of weeks.)
Cheers, -Barry
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/iane%40sussex.ac....
Security Policy: http://wiki.list.org/x/QIA9
-- Ian Eiloart Postmaster, University of Sussex +44 (0) 1273 87-3148
On Oct 21, 2013, at 03:03 PM, Ian Eiloart wrote:
Presumably, with some lists on 2.1, and others on 3.0.
That's the goal. I think it's really important to allow sysadmins to migrate lists in phases so they can gain confidence and experience with the new system without committing to it whole hog.
That would mean the admin would need to be able to specify which lists to migrate.
I guess you might want to consider whether special handling is needed for virtual domains. I know we’ve been operating a nasty cludge, where we’re using SUBDOMAIN_LISTNAME@DOMAIN for an internal representation of LISTNAME@SUBDOMAIN.DOMAIN. I suppose that’s unusual or unique, but it might be nice to allow migration of a list in 2.1 to a list with a new name in 3.0.
Sounds like we may need some hooks in the migration scripts so that admins can customize it for their needs. But in general, you're probably right that at least the migration script will need to take a source list name and migrate that to a destination list.
Cheers, -Barry
On Sat, Sep 21, 2013 at 10:48 AM, Barry Warsaw <barry@list.org> wrote:
On Sep 20, 2013, at 12:46 PM, Aurelien Bompard wrote:
What do you think? Bad timing? Any existing work I'm missing?
I am in the process of moving to a new server and I have several MM 2 mailing lists working well with virtual hosts (for my high school and college classmates). The lists are of manageable size so I can afford to do a fair amount of manual munging if need be and I want to convert to MM 3 on the new server.
Also, nothing is absolutely critical archive-wise so I can be daring in the conversion. And, too, most users rely on MS Outlook and aren't real familiar with e-mail list usage, so I think I have an ideal situation for taking notes on a real-world set up.
Are the steps needed listed somewhere?
participants (3)
-
Barry Warsaw -
Ian Eiloart -
Tom Browder