Epic Goal

• Improve the upstream project's development, planning and release internals so that it can become the origin of all work that eventually makes its way downstream

Why is this important?

• Upstream contributors today have difficulty understanding the project goals, structure, and milestones. Eventually, with improvements in this area, we want them to become meaningful contributors (looking to eventually have core project maintainers from outside the OCP OLM team)
• Downstreaming process with commit ordering and rebasing is challenging and onerous. If upstream defined a release cadence similar to Kubernetes, then the downstream product could follow those releases and no longer have the commit ordering problem that we have today.

Scenarios

1. As a project maintainer of OLM in the upstream, I want to have the source of truth for main project goals and release dates/milestones in a public space that can be easily understood and referenced.
2. As a downstream product maintainer, I want to have a seamless and easy release process that is easily (and constantly) tested and verifiable

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• OLM's source of project tracking is upstream
• OLM's release process is greatly simplified
• OLM's downstreaming process is easy to maintain and mostly automated

Dependencies (internal and external)

1. N/A

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>