Continuous Delivery
In plain terms
Keeping software always in a deployable, release-ready state.
Going deeper
Continuous Delivery automates build, test, and release prep so any approved change can go live with a single action. A human typically triggers the final release.
Under the hood
Differs from continuous deployment by keeping a manual release gate; reduces release risk and batch size.
Examples
Staging-ready builds, manual release approval, low-risk frequent releases.
Think of it like...
Like having a plane fueled and cleared, just awaiting the captain's go-ahead.