Story (Required)

As a gitops team member, I want to know what goes into the new release process and how it differs from the old release process. This is important so that nothing is forgotten and anyone can take it over with little assistance.

Background (Required)

Our new release process on konflux will need to be documented. It should live in a place easily accessible/searchable like confluence, most likely as a new part of our release manager guide. 

Out of scope

• adding applications/components
• adding customizations to build pipelines
• creating secrets
• testing release process

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

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<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