Definitions
Progressive Delivery is a GitOps term for releasing changes gradually while watching evidence and safety signals. It helps teams, humans, and agents compare declared source state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.
“The team used Progressive Delivery before lunch, so the release did not sprint into production wearing untied shoes.”
Related Terms
- Blue Green ReleaseGitOps and Release Engineering
Blue Green Release is a GitOps term for a release strategy that switches between two complete environments. It helps teams, humans, and agents compare declared source state with ru...
- Canary ReleaseGitOps and Release Engineering
Canary Release is a GitOps term for a release strategy that sends a small portion of traffic to a new version first. It helps teams, humans, and agents compare declared source stat...
- Change FreezeGitOps and Release Engineering
Change Freeze is a GitOps term for a control window that limits changes during high-risk times. It helps teams, humans, and agents compare declared source state with running system...
- Deployment WindowGitOps and Release Engineering
Deployment Window is a GitOps term for an allowed time period for applying changes. It helps teams, humans, and agents compare declared source state with running systems, then act ...
- Release FreezeGitOps and Release Engineering
Release Freeze is a GitOps term for a period when normal releases are paused to reduce risk. It helps teams, humans, and agents compare declared source state with running systems, ...
- Roll ForwardGitOps and Release Engineering
Roll Forward is a GitOps term for fixing an issue by moving to a newer corrected version instead of going backward. It helps teams, humans, and agents compare declared source state...