Brainstorm ways for background migrations to be finalized without introducing a required upgrade step
Related to !83918 (closed) where a new required upgrade path is being added that requires users install and run the background migrations from 14.9 prior to upgrading to 14.10.
Some of our previous strategies were to inline the migrations in the release that required them, but for large migrations this often has led to timeouts for end users during upgrade after an hour has passed.