On 5/7/13, Anze Staric <[email protected]> wrote: > Existing Trac installation can be either upgraded to bloodhound or > migrated to a new bloodhound_install. > [...]
> A currently missing third option is a way to move data from an > existing trac env to an existing bloodhound env (to consolidate data > from different envs to multiple projects in one env). > FWIW , we could abstract some details and work towards importing a common «data backups» format that can be generated by similar systems (including legacy Trac environments) . I've recently been reviewing Bitbucket's format , which seems to be very interesting . I'll be using it in the future . https://confluence.atlassian.com/pages/viewpage.action?pageId=330796872 http://blog.bitbucket.org/2013/04/02/finnovation-brings-you-a-heap-of-new-features/ Is there any chance for us to implement such import/export data format ? That would make Bitbucket migrations easier . Does JIRA offer a similar import / export functionality ? > I used the migration when testing upgrade to multiproduct, as all I > had was a database backup. Has anyone tried the upgrade approach > recently? I will have to upgrade a Trac 0.11 instance to BH trunk sooner rather than later . > I've tried it on an empty project created by initenv, but do > not have any real trac envs to upgrade. > FWIW I will be using the instance deployed at http://bh.web-sandbox.com . Is something like that what you are looking for ? I should also have a local version also containing pastes , and maybe a few more things . BTW , how do upgrade procedures behave with plugin data ... in practice ? -- Regards, Olemis.
