Skip to content
Snippets Groups Projects
Commit dcfed3a8 authored by Alex Ives's avatar Alex Ives :speech_balloon:
Browse files

Clarify when migrations should be squashed

Migrations should always be squashed after a required stop. Not
just when a stop is database related. Update docs to reflect
this.
parent d501513b
No related branches found
No related tags found
1 merge request!164558Clarify when migrations should be squashed
......@@ -158,8 +158,8 @@ is identified after release, the following steps must still be completed:
required stop, and the [`upgrade_path.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/upgrade_path.yml).
The `upgrade_path.yml` is the single source of truth (SSoT) for all our required stops.
1. Communicate the changes with the customer Support and Release management teams.
1. If the required stops is database related, file an issue with the Database group to
squash migrations to that version in the next release. Use this template for your issue:
1. File an issue with the Database group to squash migrations to that version in the next release. Use this
template for your issue:
```markdown
Title: `Squash migrations to <Required stop version>`
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment