OCP/Telco Definition of Done
Epic Template descriptions and documentation.

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

• Allow quay.io to support multiple backend storage options concurrently.
• R2 support is available

Why is this important?

• S3 is expensive. We can save money by moving free customers over to CloudFlare R2.

Scenarios

1. TBD

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. TBD

Previous Work (Optional):

1. TBD

Open questions::

1. Does this support signed requests?
2. Need a migration mechanism to/from R2/S3.
3. What edge cases are we going to bump into?
4. When to move to R2?
5. How to move back to S3?
6. What happens if someone upgrades from free to paid tier?

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>