[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orekit Developers] Migration to Gitlab under way...



Hi Sébastien,

On Fri, 2018-08-03 at 17:24 +0200, Sébastien Dinot wrote:

Dear all,

I just installed a Gitlab instance on our new server: https://gitlab.orekit.org/

Please, do not use it at the moment, I am carrying out some tests and the database could be reset at any time.

I am facing a problem with the issues migration. All the tools that I tried to automate the migration of issues do not work at the moment because:

I could reproduce by hand in Gitlab the 26 currently opened issues in Redmine in relation to Orekit. But I would not be able to reproduce all the comments because I would not able to impersonate all the participants. If I do that, I will appear as reporter of all issues.

Another (lazzy) strategy could be to wait the update of redmine-gitlab-migrator, the only tool that seems maintained. A blocking issue was reported few weeks ago and a contributor announced that he will provide a patch but I don't know when this patch will be available.

What is your opinion about Orekit issues? Should I ignore them at the moment? Should I import them even if I appear as their reporter?

IMHO closed issues are nice to provide a history, but not necessary for future development. Keeping the open issues necessary, but I don't think the reporter field is all that important if the reporter will still be notified when the issue is updated.

Thanks for your effort!

Best Regards,
Evan


Sébastien


-- 
Sébastien Dinot
Free Software Expert
CS SI - Space BU - Payload, Data & Applications
Parc de la Grande Plaine - 5, rue Brindejonc des Moulinais - BP 15872
31506 Toulouse Cedex 05 - France
+33 (0)5 61 17 64 48 - sebastien.dinot@c-s.fr