At present, operator release packaged as part of RHOSP is based on a release branch in midstrem sync repo (openshift/tektoncd-operator). The midstream release branches doesnot have a corresponding release in upstream repository (tektoncd/operator).

This means that there is no branch upstream to track and follow after our code freeze. In addition, we have to temporarily halt mergin new code during our code freeze deadline.

Therefore, we should define a release process based on a upstream release branch. LIke other Tekton components Operator component packaged in a productized version of RHOSP should be based on an upstream release branch.

Acceptance Criteria

• A workflow design exists to perform Productization based on a midstream branch tracking an upstream release branch
• The necessary functional components/tools are implemented and configured.