Epic Goal

• Keep MicroShift codebase up to date with upstream OpenShift components (that includes etcd and topolvm)
• Regularly produce nightly, EC, and RC RPMs

Why is this important?

• …

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Update of OpenShift components matches branching strategy
  • release-4.Y branch should be regularly updated using 4.Y nightlies
  • main branch should be regularly updated using 4.Y+1 nightlies until FF
  • release-4.Y+1 branch will be kept in sync with main automatically until FF, after FF a job for 4.Y branch must be mirrored (from job for main branch)
• Engineering Candidates (EC) based RPM builds are produced
• Nightly and RC RPMs are created for all releases
• TopoLVM is updated by CI job on a regular interval
• MicroShift's kubernetes components version matches OCP
•  

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. USHIFT-516

Open questions::

1. …

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>