Hello, welcome to the self-guided Onboarding template for productizing OpenShift Layered Services.

You are here because you are looking to productize/release an OLM-managed operator for OpenShift utilizing official productization pipelines. As part of that, certain information must be captured and processes are triggered. You use this template to work through this onboarding process. Only when this process has been completed you can productize and publish your operator.

Guidelines for using this template:
1. Clone the template by selecting 'More' -> 'Clone Operators Productization Template' from the drop-down.

2. You can find the Cloned Epic by going to Issue Links-->Clones below, then find the Epic's title  "CLONE – New [Operator Name] Productization (EPIC)". Select that Cloned Epic and update the Summary, Epic Name, and Description with your operator information.  (Note: please double check to make sure you are selecting the Cloned Epic instead of this Epic Template (PLMPGM-4951) before you make updates or move to your Jira project). 

3.a. You may move the Cloned Epic and the child tasks to your own Jira Project by using Bulk Editing

1. Search for the cloned Epic and its child tasks by typing in Search Bar: id in (your cloned Epic ID) OR id in childIssuesOf(your cloned Epic ID) order by Rank. Eg. id in (PLMPGM-3772) OR id in childIssuesOf(PLMPGM-3772) order by Rank ASC
2. Go to Tools on the top right corner
3. Bulk Change All Tasks
4. Move Tasks
5. Select your JIRA Project
6. Associate all tasks to the Epic Link

3.b. Set the Target End Date Due Date field as your estimated GA Release date (Note: Target End Date field is being utilized by the Feature Tracking Tool analysis to note the end of development date so please use Due Date field for your release date instead). Tips: if you are unsure what to set for the Due Date for now, it typically takes 60 days to productize a new operator from the Target Start Date. You may add 60 days from the Target Start Date to get the initial GA release date and set that date as your Due Date in the Epic

4. Read and follow the instructions in each task. 

PLEASE READ:

• If you are looking to productize a new operator, please review and complete ALL Tasks as part of the Epic.
• If you are looking to migrate an existing operator to Konflux, you may skip and close Task 1-6,9a,10 as they may not be applicable to you but please review and decide for your operators.

5. Assign Jira tasks to the appropriate team member and keep a record in Jira of what's been done before closing out. If a decision was made to not complete a task please comment on the reasoning and risk assessment carried out.

6. Please ensure there are labels "OperatorProductization"  on the Epic (and "new-operator" label for new operators)

7. If you have any questions, please reach out to the Program Manager for assistance or Ramona Sidharta

Resources:

• https://konflux-ci.dev/docs/advanced-how-tos/building-olm/
• https://docs.engineering.redhat.com/display/CFC/Best_Practices