Story (Required)

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

As a Red Hat Engineer trying to provide z-stream support I want "builds for OpenShift" to point to the appropriate upstream release branch

Background (Required)

<Describes the context or background related to this story>

Upstream will be defining release branches for backports.
We need to update CPaaS to point to the upstream release branches (ex: release-v0.12) so we only pull in backports when releasing 1.0.1

Out of scope

<Defines what is not included in this story>

• CVE backports upstream
• Passing CVP checks related to

Approach (Required)

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

Once upstream release branches are created, point CPaaS to use the new release branch.

Dependencies

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

Upstream release branches set up

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>

• CPaaS uses the following release branches for 1.0 z-stream builds:
  • shipwright-io/build: release-v0.12
  • shipwright-io/operator: release-v0.12
  • shipwright-io/cli: release-v012.
• CPaaS can build container images from the above branches

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