Document how to communicate MRs with larger database migrations
I am not sure if and where to best communicate the fact a rather long running or otherwise impactful database migration has been merged and is about to be deployed to GitLab.com. At times, I felt it'd be good to sync up with the Delivery team to understand whether or not the timing is right to merge and deploy a large migration to the site. However, I'm not sure if it's actually relevant or helpful at all.
@gitlab-org/delivery Do you find it useful to know about larger migrations upfront? If yes, how and when do we best communicate this?
At best we wouldn't have to worry about this and things would just go in as the are merged. However, I was under the impression that we still have times where we may want to coordinate this more carefully. Is that a false interpretation on my end?