Owner: Architect:

Feny

Story (Required)

As an SBO Engineer I would like to be able to release 1.2

Background (Required)

We need to release 1.2 using the new process, where Upstream is Released First including GitHub release tagging. The we move to release downstream. Lastly we deploy to Dev Sandbox staging and production. If downstream fails for whatever reason a new patch release is needed for upstream. This will require cherrypicking fixes to release branch. I something goes wrong on dev sandbox a new patch release is need for upstream and downstream.

Glossary

NA

Out of scope

NA

In Scope

Release Notes for Upstream will need to be added to this story which will be pickup by docs team to set release not for 1.2

Approach(Required)

Follow checklist being created here: APPSVC-1153

Items to tick off depending on the type of Release:

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

 
(?)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 Makefile
• Add doc branch to antora files
• Create and update docs branch

• 1.4 Configure Errata
• Create a new Advisory 
• Assign QE , DOC and Security team.

• 2.Release Downstream
• 2.1 General Process
• Send Merge request to CPAAS team
• Send Patchset for Operator to gerrit
• Send Patchset for Bundle to gerrit
• Check the brew builds and attach to errata
• Request Docs review and assign to QE

• 2.2 QE Checklist
• Ensure Images passed and trigger pipelines
• Check for IBM Z and P acceptance tests
• Move the errata to REL_PREP
• If security release - get approval from security team

• 3. Release Upstream
• Check if Helmchart is created
• File a PR 
• check operatorhub.io when merged

• 4. Github
• Create new tag
• Add release notes.
• Add release artifacts

• Other release Activities
• Testing in Dev Sandbox
• To communicate with other components/projects like ODO,ODC
• Closing jira releases and github milestones . 

Demo requirements(Required)

None

Dependencies

None

Edge Case

NA

Acceptance Criteria

We have release 1.2.x upstream as required to pass all the requirements for upstream release
We have release 1.2.x upstream following Errata process
We have update Dev Sandbox staging and production
Documentation: Yes

Upstream: Release Notes including all changes since last Release

Downstream: Release Notes including all changes since last Release

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

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied