3 ms·

I personally find them frustrating because they throw off our regular release cycle. Sure, we didn't deploy any potentially buggy work (or any fixes for known b

I personally find them frustrating because they throw off our regular release cycle. Sure, we didn't deploy any potentially buggy work (or any fixes for known bugs...), but now we have to manage a giant release when we 'thaw'. And make sure no work gets left out, which is more likely since we're off our normal cadence.

layoric 5y ago
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.