Post #1705844

@treuss TL.DR: Read through all release notes and perform all steps unique to each set of notes, as well as all steps common to all release notes. You can do a direct upgrade, but only if all of the release notes for each upgrade shows that the steps are the same. The real big thing is pre and post migrations. You must do these for most anything major. However, some versions require extra steps beyond these, and they would need to be completed during the upgrade to the final target release, even if they do not apply to that release. For example, a while ago, some secrets were required to be added to the env.production file. Many mastoadmins got caught here, as they would have skipped the version requiring these keys added, and then they would not have seen this requirement in the final release notes of the target version they were upgrading to, and thus would have resulted in a broken installation until this step was completed.