-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
ACM adoption
-
False
-
None
-
False
-
Not Selected
-
To Do
Epic Goal
Discuss with policy and app squad to see the potential opportunities for maestro. What benefits we can have if adopting the maestro. What're efforts if adopting the maestro?
Why is this important?
...
Scenarios
- Discuss with policy team for potential opportunity for maestro
- Discuss with app team for potential opportunity for maestro
Acceptance Criteria
...
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.