Goal

The goal of removing oc-mirror from the OCP payload is to reduce redundant work needed currently which could be avoided if oc-mirror was out of the OCP payload. Since oc-mirror is not a component that will stop the operation of openshift in case it is not inside of the payload, it is feasible to have it outside.

Benefit Hypothesis:

• It is possible to have only one version of oc-mirror that supports all supported Openshift Versions

• • It would remove the time from QE and Software engineer on doing back porting and bug fixes would get customers faster
  • It would be easier for docs team to maintain only one documentation instead of one per version
  • It would be easier for customers to find the correct documentation since only one is needed
• It is possible to have shorter releases cadences

• • Since the release cycle is not attached to Openshift, it is possible to deliver features, bug fixes and improvements faster

Resources

Add any resources (docs, slides, etc.) pertinent to the definition of the work. These might not be known until later. Update as necessary.

Responsibilities

CID, Konflux and ART team

Success Criteria

oc-mirror is not included in the OCP payload and has its own release process and cycle.

Results

Add results here once the Initiative is started. Recommend discussions & updates once per quarter in bullets.