Story (Required)

As a release engineer, I want to ensure that all JIRA epics and stories targeted for 1.15.0 release is in COMPLETED state and the release 1.15.0 version is marked as done in the JIRA releases page.

Background (Required)

The status of JIRA epics and stories should reflect the actual state. It should all be closed and the release should be marked as released so that any stakeholder viewing the various dashboard, knows the status of the epics and stories.

Out of scope

NA

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

Release should have been completed and the errata should be in SHIPPED_LIVE state.

Acceptance Criteria (Mandatory)

• All 1.15.0 JIRA epics and stories are marked as done.
• Release 1.15.0 in JIRA is marked as released.

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

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