Add more installation automation
We don't recommend jumping between several versions of GitLab in our maintenance documentation. This can be painful if an instance has been sitting un-updated for an extended period of time. We should consider options to make this less painful.
I think an initial first step is a script to figure out the next version to install. So if someone were to run apt-get install -y gitlab-ee$(gitlab-ctl next-version)
they should be reasonably sure they can seamlessly upgrade. They could repeatedly run that script until it finds no new version to install to get to the latest. How to handle major releases is up for debate. We may consider making the script exit non-zero if a major release is next, forcing a manual upgrade.
Past that, we could leverage the bundled go-crond
and kubernetes cronjobs to provide users an optional way to easily automate this. I would strongly advocate for this being off by default, but something that is easy to enable.