GitLab

Created by: frlan

When following the upgrade-notes from doc folder it appears that needed updates for e.g. git are recognized at the point, when the upgrade is failing. It would be better, to have a note similar to installation howto into the upgrade-documentations

Created by: Razer6

@frlan When do updates fail due to git version?

By Administrator on 2013-09-13T10:37:20 (imported from GitLab project)

Created by: frlan

IIRC the update to 5.4 needed an git >= 1.7.10, before everything went fine with <1.7.10

By Administrator on 2013-09-13T10:57:32 (imported from GitLab project)

Created by: frlan

Also the upgrade to ruby >2.0 is not mentioned in howtos (at least not as prominent as I was able to found them)

By Administrator on 2013-09-13T11:00:54 (imported from GitLab project)

Created by: Razer6

@frian You're right with git. But the check-task after migration would complain about the git version. Feel free to create a PR!

Ruby 1.9.3 is still supported!

By Administrator on 2013-09-13T11:03:01 (imported from GitLab project)

Created by: frlan

The idea behind that report is to have kind of a checklist before starting the upgrade and not failing in the way.

By Administrator on 2013-09-13T11:04:37 (imported from GitLab project)

Created by: Razer6

There is now documentation to ensure the right versions are installed

By Administrator on 2013-10-28T07:03:14 (imported from GitLab project)