Epic Goal

• Identify all the steps needed to switch CPaaS (along with Honeybadger, Comet, etc..) to single stream
• Stage those changes in case when decide to move forward
• Coordinate with all other functions to make sure the change is understood.

Why is this important?

•  We are probably moving into a single stream soon. It will simplify upgrades and be easier to understand for users
• CPaaS changes are needed

Acceptance Criteria

• We must have a list of steps needed to turn CPaaS into single stream
• All those changes must be in place

Dependencies (internal and external)

1. Switch branching process upstream to use master for releases and pre-merge test on feature branches (KATA-1799, KATA-1822)
2. Change master to main (KATA-1818)
3. Update midstream to use main and tags (KATA-1800)

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>