3 ms·

All you have to say is "rolling release," or "why releasing according to lunar phase is dumb." That you need to explain it the way you did is another example o

• shoo 4y ago
  I've worked in a similar environment. The motivation to batch releases was largely driven by a desire to do full end-to-end integration testing of changes between a number of entangled backend and frontend systems. It often took days to stabilise all the components in the single pre-production staging environment used for end to end integration testing, then run through the test plan. Perform batched end-to-end testing of system was the process bottleneck. Monthly releases created similar crunch dynamics of changes being delayed by a month if they weren't stable enough to enter the monthly test cycle. Since end to end testing is the bottleneck, you don't want to feed in low quality inputs (rushed changes that are likely to cause issues and then trigger re-tests of the entire slow end to end test process). I'm not saying this is the best way to do this, it definitely isn't, but there can be some reasoning behind it.