#release

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 running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.

“The team used Blue Green Release before lunch, so the release did not sprint into production wearing untied shoes.”

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 state with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.

“The team used Canary Release before lunch, so the release did not sprint into production wearing untied shoes.”

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 systems, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.

“The team used Change Freeze before lunch, so the release did not sprint into production wearing untied shoes.”

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 without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.

“The team used Deployment Window before lunch, so the release did not sprint into production wearing untied shoes.”

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.”

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, then act without pretending a deployment did more than the evidence shows. Source context: OpenGitOps principles.

“The team used Release Freeze before lunch, so the release did not sprint into production wearing untied shoes.”

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 with running systems, then act without pretending a deployment did more than the evidence shows. Source context: Argo CD documentation.

“The team used Roll Forward before lunch, so the release did not sprint into production wearing untied shoes.”

Rollback is a GitOps term for returning to a previous known configuration or artifact version. 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 Rollback before lunch, so the release did not sprint into production wearing untied shoes.”