> If you then add additional stages, you can have it spend 8 hours on each stage, deploying to prod every 8 hours, so a higher frequency, but any given build is

> If you then add additional stages, you can have it spend 8 hours on each stage, deploying to prod every 8 hours, so a higher frequency, but any given build is still preprod for 24 hours, so frequency has tripled without a change in latency. Got it, thanks for the clarification. I'd interpreted your argument as: each stage is a deployment, therefore deployment frequency goes up (which also, of course, would mean lead time goes down -- so I was confused). I like that this scheme could maintain continuous integration by having the "B" staging include the patch under test in "C" -- clever solution!