Re: [Orekit Users] [Orekit Developers] forge migration to be expected soon

[Luc Maisonobe <Luc.Maisonobe@c-s.fr>]

Le 26/06/2014 10:13, Luc Maisonobe a écrit :
> Le 24/06/2014 14:39, Luc Maisonobe a écrit :
>> Hi all,
>>
>> Since a few years, the Orekit project has used the Chiliproject forge,
>> which is a fork of the Redmine forge. As the development of Chiliproject
>> has stopped and as Redmine has integrated back the various changes from
>> the fork, we are going to switch back to Redmine.
>>
>> The time frame for the migration is around the start of next week.
>> We don't expect the migration to exceed one or two days. The Orekit
>> server will be unavailable during the migration. Both the forge and git
>> repository will be unavailable. The mailing lists should be unaffected.
> 
> The migration should occur over the week-end.

The migration has been partially done.
Some parts are back online, but there are many problems left, we are
sorry about that. We hope to solve the remaining probles in the upcoming
days, but wanted to bring the site back to live as soon as possible so
users can at least work.

As explained before, the various git repositories (for example orekit
but also the SOCIS sub-projects) have been renamed. In order to get the
definitive URL, please go the the front page of each project (i.e.
<https://www.orekit.org/forge/projects/orekit>,
<https://www.orekit.org/forge/projects/socis-2014-database>,
<https://www.orekit.org/forge/projects/socis-2014-demo> ...) and look at
the grey panel on the bottom left: the new URL is shown here. If you are
logged into the forge and have write access, you will be able to switch
between the two protocols SSH and HTTPS to display the appropriate Git
repository URL for you. If you are not logged or don't have write
access, you will only see the HTTPS read-only access. Note the you
should use HTTPS and not HTTP.

The wiki is not properly formatted yet and the links to images have
disappeared. The reason for this behaviour is that the Markdown dialect
used by the forge and the one used by the maven plugin are not fully
compatible. We will try fo fix it as soon as possible.

We apologize for the inconvenience

Luc

> 
> Luc
> 
>>
>> After migration, the new forge will contain the same projects,
>> sub-projects, users, passwords, issues, ... The look and feel will be
>> slightly different. The wiki syntax will be changed from Textile to
>> Markdown (we will take care to convert the pages, but perhaps not
>> immediately, so you may experience some weird layout in the wiki for a
>> few days after migration).
>>
>> One important change is that the last part of the URL for Git access
>> will change. Redmine does not allow the Git repository to have exactly
>> the same name as the project, so we have to rename the repository. In
>> order to update the connection between your local repository and the
>> main one on our server, you will have to run something similar to the
>> following:
>>
>>  updating access to read-only repository (http), assuming it is
>>  referred to as "origin":
>>
>>  git remote set-url origin http://www.orekit.org/git/orekit-main
>>
>>
>>  updating access to read-write repository (ssh), assuming it is
>>  referred to as "origin":
>>
>>  git remote set-url origin ssh://git@www.orekit.org/orekit-main.git
>>
>>
>> We are sorry for the inconvenience.
>>
>> Luc, on behalf of the Orekit team
>>
>