Update and create consistent upgrade documentation
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Description
A customer reached out to make the upgrade documentation more consistent:
To complicate matters, we found your update documentation to be inconsistent and confusing. There are several different sections in the update instructions that could have possibly applied to our situation, and yet without any conclusive criteria for deciding which to choose. One section, "Updating by Manually Downloading the Official Repositories" makes mention only of the
rpm -Uvhcommand -- nothing about either skip-auto-migrations or gitlab-ctl reconfigure. The second, "Updating from Gitlab 6.6 and higher to 7.10 or newer," mentions the skip-auto-migrations file, but it also suggests that GitLab will automatically reconfigure The third, Updating from Gitlab 6.6 and higher to the latest version" seems to suggest you have to run "gitlab-ctl reconfigure," that migrations have to be run, but makes no mention of the skip-auto-migrations file.
Proposal
Update documentation to include whether commands can be used in previous versions and include commands to upgrade upgrades through the package manager.