shipping-and-launch

A pre-deploy ship plan coordinates gates, rollback, observability, and release notes for Spring Boot 4 features. It generates a ready-to-execute ship plan artifact with staged rollout and abort criteria for human approval.

Yes, the structured pre-ship plan applies to both brownfield and greenfield projects. It formalizes a documented rollback strategy and staged canary rollout plan with explicit abort criteria before shipping.

Pre-ship gate verification checks Validation, Code Review, Open Questions, Baseline, and Diff Scope. It enforces green status across all gates to prevent unplanned shipping of features.

Observability sign-off requires documenting metrics, logs, and dashboard references to ensure visibility after deployment. It verifies monitoring is configured before the staged rollout begins.

Release notes generation communicates changes to users and stakeholders during the ship workflow. It is produced automatically from the ship plan template alongside rollout and observability artifacts.

Run the ship workflow after code review to generate a complete release plan. This ensures all pre-deploy hygiene, including gate verification and rollback documentation, is finalized before shipping.