Automate upgrade stop planning process
Current process
- raise issue to collect requirements from all development teams for a potential upgrade stop
- announcement internally to ensure that everyone is aware which stop to target
- raise issue to update Omnibus in the release following the required stop
- raise issue for Charts in the release following the required stop
- raise issue for Gitlab::Database::MIN_SCHEMA_GITLAB_VERSION in the release following the required stop
- File an issue with the Database group to squash migrations to that version in the next release. (Details on Step 3)
- create issue for Upgrade path in https://gitlab.com/gitlab-com/support/toolbox/upgrade-path
- create issue for GitLab docs update at https://docs.gitlab.com/ee/update/#upgrade-paths
Steps 3-7 could be automated by Standardize upgrade path information (#420831 - closed)
Edited by Peter Lu