Define a rollback policy in case of incompatible schema changes

[incident-io]

In case of schema changes that remove columns or tables, we should have a clear message that rolling back to a previous version should not be the first option because rollback migration scripts do not exist in the previous one.

Example #12873

---

This action was created from Incident 249 by Alejandro de Brito Fontes, using incident.io 🔥

[vulkoingim]

As an addition to this - I would recommend revisiting how features, especially ones that rely on DB migrations are deprecated. Specifically destructive actions - in this instance a column removal, should never happen at the same time the feature is deprecated. For self-hosted releases there should be at least 1 release between the removal of the feature and the destructive action in order to avoid incidents like this one.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.