Story (Required)

Release Builds v1.0.1 to customers!

<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?>

Background (Required)

<Describes the context or background related to this story>

v1.0.1 includes important CVE fixes that are backported upstream

Out of scope

<Defines what is not included in this story>

• Other operator-specific bugs previously identified in v1.0.0. This is primarily a security advisory.

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 branches are set up in BUILD-788, pull in upstream commits with fixes for linked blocker CVEs
• Perform actions necessary for release:
  • Draft errata, linking CVE fixes. Add summary describing bug fixes and security advisories.
  • QE verifies build and moves release to "ready" state.
  • Engineering indicates a release date, marks it as good to go. Current proposed release date is March 21, 2024
• Errata description is used to draft release note in product documentation

Dependencies

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

• BUILD-851
• BUILD-896
• BUILD-786
• BUILD-852
• BUILD-853

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>

• Builds operator released with v1.0.1
• Available in OperatorHub for OCP 4.14 and OCP 4.15
• Release notes for v1.0.1 published on the Builds documentation

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Estimation:

Engineering: 2
Docs: 2
QE: 1
PX: 0 (covered by docs)
Security: 0 (covered by RHSA/errata)

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