Stefano Maffulli wrote: > I think the best option then is to clone openstack@launchpad in the new > host and leave operators as is (at least for the moment). Suboptimal, > maybe, but I believe it solves the issue at hand (consolidate lists on > one host) and doens't create extra work or stress. > > If nobody stops me, I'll go on and contact Canonical's folks to get > more details and will post a migration plan to this list soon.
I think that's a safe bet. For those following at home, that would be option A2, which can potentially be turned into option B2 by merging openstack-operators@ into openstack@ in the future. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
