Upgrades should be aware of the upgrade path
We have specific upgrade paths that we tell customers to follow when performing upgrades. Right now, there is no real enforcement of that. Customers can and do upgrade through required stops. Although this is sometimes "Okay" it's not recommended and could lead to unexpected issues.
Proposal
We should make gitlab upgrades aware of the path, and prevent or at least warn customers about upgrading between unsupported jumps. For example: A customer running 15.9 tries to upgrade to 16.1, the upgrade scripts throw an error and say they have to upgrade to 15.11 first instead.
@twk3 @plu8 @dorrino is this feasible? It seems like it could be problematic that folks can jump between versions unaware that they maybe should have stopped at a different one.