Epic Goal

• SQlite catalog maintainers need a solution to facilitate veneer adoption.  There is a lot of excitement around the use of semver for bundle version expression and the ability to have the opinionated generator handle so much of the grunt work in producing an FBC catalog contribution.

Why is this important?

• Minimizing friction to veneer adoption is key to speeding the FBC transition.  Supporting a transition mechanism built into opm is vastly preferable to a chained sequence of utilities/scripts. 

Scenarios

1. Maintainer wants to update legacy catalog to semver veneer
2. operator author wants to update their catalog contribution to semver veneer

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Documentation - MUST have supporting documentation easily available to catalog maintainers & operator authors upstream
•  

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>