Another option is (if possible) not to have a release cadence in the first place. If deployments are happening regularly everyday as a part of small PRs, you ju

Another option is (if possible) not to have a release cadence in the first place. If deployments are happening regularly everyday as a part of small PRs, you just get a backlog of code reviews. Sure some releases will require orchestration where order is important but better than one giant release. DB migrations are a different story imo, and should get more planning. I’m guessing there would be other stacks/domains where regular release intervals suit customers better though.