Epic Goal

• Prepare the Compliance Operator and File Integrity Operators for a v1.0 stream.

Why is this important?

• We've been releasing 0.1.x versions for both operators, but this was subtly breaking the contract of semver, and makes it difficult to plan forward based on the version (this will be important as we transition into no-FF). It should follow:
• * major number accommodates backwards-incompatible features.
• * minor indicates new features.
• * release number indicates new non-feature changes, CVE, and bug fixes.

By calling 1.0, we'll then begin to follow the proper semantics of semver, and this will allow us to plan our releases properly.

Dependencies (internal and external)

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>