Outcome Overview

Successfully migrating OLMv1's origin-based tests to the downstream operator-framework-operator-controller repository will significantly improve development efficiency and reduce CI costs. This move will decrease the time spent on test investigations and overrides, enabling faster iteration and delivery of features. It will also reduce the number of pull requests and CI runs required for changes that involve both origin and the component, streamlining the development process and freeing up developer time.

Success Criteria

For this outcome to be considered a success, all existing OLMv1 origin tests must be successfully provided by a test extension binary within the operator-framework-operator-controller repository. This transition must be completed without any tests being temporarily disabled, and without negatively impacting our component readiness measurements.

Expected Results (what, how, when)

• Reduced developer friction: We expect to reduce the average number of PRs required for changes involving both origin and the component from three to one. This will be measured by analyzing PR history for related changes over the 90 days following the migration.

• Decreased CI costs: We anticipate a measurable decrease in CI resource usage and costs associated with OLMv1-related changes. We will track and compare CI run times and resource consumption for these tests for 90 days after the migration is complete.

• Improved developer velocity: By reducing the time developers spend waiting on CI runs and investigating unrelated failures, we expect to see an increase in the number of OLMv1 features and fixes delivered per quarter. We will measure this by tracking the number of closed tickets for OLMv1-related work in the 90 days following the migration.

Post Completion Review – Actual Results

(This section will be filled out after the work is completed and the measurements have been reviewed.)

Disclaimer: This text was generated with the assistance of an AI and has been reviewed for accuracy.