A GitLab user has expressed the following about the documentation suite: `Further none of those pages explains how to pass in a specific version of the omnibus package to satisfy the upgrade process in the even that the latest version fails because the upgrade version differential is not supported.` This was posted here: https://news.ycombinator.com/item?id=18027577. We need to make the documentation explain all information required during upgrade process to make the upgrade process as smooth as possible. ## New doc or update? - [ ] New documentation - [X] Update existing documentation ## Checklists ### Product Manager <!-- Reference: https://docs.gitlab.com/ee/development/documentation/workflow.html#1-product-manager-s-role-in-the-documentation-process --> - [ ] Add the correct labels - [ ] Add the correct milestone - [ ] Indicate the correct document/directory for this feature <!-- (ping the tech writers for help if you're not sure) --> - [ ] Fill the doc blurb below #### Documentation blurb <!-- Documentation template: https://docs.gitlab.com/ee/development/documentation/structure.html#documentation-template-for-new-docs --> - Doc **title** <!-- write the doc title here --> - Feature **overview/description** <!-- Write the feature overview here --> - Feature **use cases** <!-- Write the use cases here --> ### Developer <!-- Reference: https://docs.gitlab.com/ee/development/documentation/workflow.html#2-developer-s-role-in-the-documentation-process --> - [ ] Copy the doc blurb above and paste it into the doc - [ ] Write the tutorial - explain how to use the feature - [ ] Submit the MR using the appropriate MR description template