Hi all!
With our infra/toolchain now being fully prepared for the Git migration, I can finally say that there are no more blockers holding us back. Therefore I'm announcing that the migration from SVN to Git will take place on
TUESDAY, OCTOBER 3, 2017
During that day (European time) SVN will be turned read-only forever and some of our services may expect temporary downtime. Let's see who will get the last commit ever to SVN :)
The new repository will then be available at https://github.com/reactos/reactos, with https://git.reactos.org providing a mirror.
The following things are still on the To-Do list, but I don't consider them blockers. We can work on them iteratively after the migration:
* Writing a new .gitignore file. * Writing a .gitattributes file to enforce EOL style. * Writing Git guides on our Wiki for beginners and SVN users.
Best regards,
Colin
What about code.reactos.org ??
On Sep 21, 2017 11:40 AM, "Colin Finck" colin@reactos.org wrote:
Hi all!
With our infra/toolchain now being fully prepared for the Git migration, I can finally say that there are no more blockers holding us back. Therefore I'm announcing that the migration from SVN to Git will take place on
TUESDAY, OCTOBER 3, 2017During that day (European time) SVN will be turned read-only forever and some of our services may expect temporary downtime. Let's see who will get the last commit ever to SVN :)
The new repository will then be available at https://github.com/reactos/reactos, with https://git.reactos.org providing a mirror.
The following things are still on the To-Do list, but I don't consider them blockers. We can work on them iteratively after the migration:
- Writing a new .gitignore file.
- Writing a .gitattributes file to enforce EOL style.
- Writing Git guides on our Wiki for beginners and SVN users.
Best regards,
Colin
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Am 21.09.2017 um 21:07 schrieb encoded:
What about code.reactos.org ??
FishEye is one of the services that will be temporarily taken down during the migration and restarted, then indexing the Git repo instead of the SVN one. Just like the rest of our services. Nothing special about it.
- Colin