Epic Goal

• Delineate between community and enterprise distributions of MicroShift by excluding selected MicroShift components from community builds
• Keep MicroShift's footprint as low as possible
• Keep complexity low. Do not create a fork or side-stream of openshift/microshift right now

Why is this important?

• We only need to include redistributable upstream components in the community builds

Scenarios

1. As an alternative to creating an "upstream" microshift repo, we re-implement certain component (e.g. LVMS) support that was previously in MicroShift
2. Once the plumbing is setup, and with appropriate community documentation, it should be a simple `make COMMUNITY=true' build flow.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

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>