-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Podman machine OS
-
False
-
None
-
False
-
Not Selected
-
To Do
-
rhel-sst-container-tools
-
50% To Do, 0% In Progress, 50% Done
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 users to customize and build their own podman machine operating systems
Why is this important?
- podman machine is a strategic component for outreach to MacOS and Windows developers.
- this embraces the use of ostree as an OCI image as part of our lont-term strategy aligning ourselves with other technologies important to Red Hat.
Scenarios
- A developer wants to add a specific package to his or her operating system (podman machine os build)
- A developer wants to revert the machine operating system because it is not functioning as expected (podman machine os revert)
- A colleague develops a new machine OS OCI image and I want to install it on my podman machine.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>