Owner: Architect:

ansadler@redhat.com 

Story (Required)

As an SBO Developer I would like to release SBO 1.3.1

Background (Required)

TBD

Out of scope

Helm Chart

In Scope

Upstream release
Downstream release

Approach(Required)

Productization process in details

Demo requirements(Required)

No Demo

Acceptance Criteria

Development:

• SBO 1.3.1 Is Available in OperatorHub and ArtifactHub
• SBO 1.3.1 is available in redhat-operators catalog source in OpenShift 4.9, 4.10, 4.11 (required) and 4.12
• Release notes updated

QE:

• Acceptance tests with x86_64 architecture PASSED
• Acceptance tests with ppc64le (IBM Power) architecture PASSED
• Acceptance tests with s390x (IBM Z) architecture PASSED
• Acceptance tests with aarch64 (ARM64) architecture PASSED
• Performance evaluation PASSED

Documentation: Yes (needs-docs|upstream-docs)

• Upstream: Review Required

• Downstream: Yes

Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>

Release Checklist

Items to tick off depending on the type of Release:

• For an Upstream + Downstream Release , You need to tick off all the items in the Order of Step 1, 2 , 3, 4.
• For an Upstream only Release , You need to Tick off Steps 1.1, 2, 3.

Steps

• 1.Preparation steps
  • 1.1 Take ownership of a Release Jira ticket
  • 1.2 Communicate about Helm chart and docs
  • 1.3 Bump product version
    • Create PR to update version in Makefile: https://github.com/redhat-developer/service-binding-operator/pull/1283
    • Add release branch to antora files
    • Create and update docs in release branch
• 2. Release Upstream
  • Check if Helmchart is created
  • File a PR to operatorhub.io: https://github.com/k8s-operatorhub/community-operators/pull/1862
  • Check operatorhub.io when merged
• 3. Github
  • Create new tag
  • Add release notes.
  • Add release artifacts
• 4.Downstream
  • 4.0 Configure Errata
    • Create a new Advisory: https://errata.devel.redhat.com/advisory/103752
    • Assign QE , Doc (and Security team if security release)
    • Inform Release team (Matej Krasnican on Google Chat) about the planned release (informed via slack)
  • 4.1 General Process
    • Send Merge request to CPaaS: https://gitlab.cee.redhat.com/cpaas-products/ocp-tools-sbo/-/commit/f420bf52cf8593d680cdd137a180ea5808a89b6e
    • Send Patchset for Operator to gerrit: https://code.engineering.redhat.com/gerrit/c/service-binding-operator/+/432290
    • Send Patchset for Bundle to gerrit: https://code.engineering.redhat.com/gerrit/c/service-binding-operator/+/432478
    • Check the brew builds and attach to errata
    • Request Docs review and assign to QE
  • 4.2 QE Checklist
    • Ensure CVP passed and trigger pipelines
    • Ask IBM Z and P to run acceptance tests (Attach tarballs with results to the ticket)
    • Move the errata to REL_PREP
    • If security release - get approval from security team

• Other release Activities
  • Deploy/Update in Dev Sandbox
  • Communicate with other components/projects like ODO,ODC
  • Close jira releases and github milestones

Legend

Unknown

Verified

Unsatisfied