Hi, On Thu, Oct 31, 2013 at 08:58:00PM +0100, Sylvain wrote: > On Wed, Oct 30, 2013 at 04:01:16PM +0100, Roland Mas wrote: > > Sylvain, 2013-10-29 20:44:27 +0100 : > > > One thing that will help is assessing how difficult it will be to > > > migrate. In particular, did any of you already wrote migration scripts > > > for the forges fusioned in FusionForge? > > > > I once wrote Perl+SQL scripts to migrate from the (proprietary) GForge > > AS to the current (at the time) FusionForge, so it's definitely doable, > > but not really something I'd look forward to. > > > > On the other hand, during the Coclico project, we ended up with an > > implementation of project import/export for FusionForge, with an > > intermediate format that was not specific to FusionForge. Maybe that > > would be worth looking into? I guess that the “only” missing part would > > be the exporter from Savane. That would also eliminate the problem of > > having both the source and destination databases on the same DB server. > > It has this pro, and I'll check this nice idea - but I'm afraid it may > not preserve the bug IDs.
After giving it some more thought, I'm more inclined to perform a MySQL->MySQL, Savane->FusionForge migration, and then a MySQL->PGSQL such as http://tapoueh.org/blog/2013/08/08-MySQL-to-PostgreSQL.html. Comments? :) -- Sylvain _______________________________________________ Fusionforge-general mailing list [email protected] http://lists.fusionforge.org/cgi-bin/mailman/listinfo/fusionforge-general
