Feature Overview (mandatory - Complete while in New status)
We need to work with the RHOAI team to have them adopt our base images for their builds.

Goals (mandatory - Complete while in New status)

Set up infrastructure and build a wheel collection for the Tensorflow image in RHOAI, then help them update their image to use our base images and the collection for all supported variants (priority is ROCm for now, but we also need builds for CUDA).

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):
All variants supported by RHOAI use wheels built by an AIPCC pipeline.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
As a RHOAI developer I can trigger builds of wheels and manage the versions used.

Out of Scope {}{}(Initial completion while in Refinement status):
Replacing the image build pipelines used by the RHOAI team

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

Questions to Answer {}{}(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations {}{}(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

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.