Feature Overview (mandatory - Complete while in New status)
We want to build a fresh set of RHEL AI and RHAIIS images every night using the latest commit in the "main" branch of the upstream git repositories so we can identify build issues more quickly and so we can provide images to the field team for use in proof-of-concept deployments. Using nightly builds instead of official releases means that as bug fixes or incremental feature work is completed we can deliver that work to the field for use with prospective customers.

Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature

Provide nightly images to QE for testing.

Provide nightly images to the field team, but not directly to customers with subscriptions, so the field does not have to wait for minor or z-stream releases when working on proof-of-concept deployments.

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):
Field team members can deploy a nightly build of RHEL AI or RHAIIS as part of a PoC for a customer.

QE can test pre-release builds of RHEL AI or RHAIIS produced daily.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
As a Red Hat field representative, I can access a nightly build of RHEL AI or RHAIIS to show a customer a proof-of-concept deployment using unreleased features.

Out of Scope _{}(Initial completion while in Refinement status):{_}
Due to their size, we will not build installation artifacts for RHEL AI. We will only build the bootc and application images. To consume the images, a user will need an installer for an older version of the software, from which they can switch to the nightly image channel and update to a specific nightly or the latest nightly.

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

We will need documentation for the field team to understand how to access the images, but that information should not go into the product documentation.

Questions to Answer _{}(Initial completion while in Refinement status):{_}
1. Do we want to build the nightly wheels using the same pipeline and package index that we use for production builds, or do we want to set up a different pipeline?

2. If we use a separate pipeline, how do we use the separate wheel collection releases as part of the build for the images for RHEL AI?

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 Planning 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

• …