Feature Overview (mandatory - Complete while in New status)

IBM has requested support for IBM z-series in RHELAI. This requires the AIPCC team to build packages for IBM z. This work includes confirming functionlity of wheels and rpms that the AIPCC team builds.

The IBM z-series team will be responsible for providing source code for shipped packages, and providing modifications to CI/CD to build packages within our infrastructure. This may or may not require z-based VMs, z-hardware, etc.

Goals (mandatory - Complete while in New status)

• Support IBM team building RHEL AI for Z

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

Full RHEL AI builds for Z are released

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):

Out of Scope {}{}(Initial completion while in Refinement status):

• IBM will be doing most of the work, so we expect to only need to review their changes.

Documentation Considerations {}{}(Initial completion while in Refinement status):

N/A

Questions to Answer {}{}(Initial completion while in Refinement status):

Background and Strategic Fit (Initial completion while in Refinement status):

Customer Considerations {}{}(Initial completion while in Refinement status):

N/A

Team Sign Off (Completion while in Refinement status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

*An engineer or tech lead from the product requesting this feature is required for the signoff below.

• …