Story (Required)

Integrate release test pipeline for the next branch and, upon stabilization, extend integration for 1.20 and 1.21. The test is currently optional but will become mandatory once validated for stability.

Acceptance Criteria (Mandatory)

• Pipeline Integration

• • The release test pipeline is successfully integrated and triggered for the next branch.

• • Upon stabilization, the same pipeline integration is extended for 1.20 and 1.21.

• Release Gate Integration

• • Initially, the release test pipeline remains optional for release blocking.

• • Once stability is verified, the pipeline becomes a mandatory gate for release readiness validation .

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met