Start tracking the time it takes to run migrations
Every month for the release post I'm asked how long the downtime process would take if needed. Every month I have to make a rough estimate on what I remember the various migrations taking in terms of time. We should start tracking migration timings somewhere and save them for later review. Perhaps the easiest way is to just copy the migration output log (which contains the timings) to some shared folder grouped per version.