Software delivery

This category owns the path from an integrated source change to a production release and its recovery plan.

It covers promotion evidence, deployment automation, rollout control, compatibility windows, and release verification.

Testing entries own test strategy and evidence generation. Practice entries own techniques that apply beyond delivery. Delivery entries connect those techniques to promotion and production change management.

Entries (5)

Backward-compatible deployment and expand-contract changesChange contracts in stages so old and new software can coexist safely during a deployment or migration window.

Continuous delivery versus continuous deploymentDecide whether validated release candidates wait for an explicit production decision or deploy automatically after all promotion gates pass.

Continuous integration and quality gatesIntegrate changes frequently and require reproducible evidence before a shared branch or artifact is eligible for promotion.

Feature flags and controlled rolloutSeparate deployment from user-visible release by placing temporary runtime control around selected behavior.

Rollback, roll-forward, and release verificationVerify production behavior after deployment and choose a recovery path that matches the reversibility of the change.