Feature Overview:

Given the fast paced releases with vLLM and LLM-D, the RHAIIS team has proposed that we maintain 3 separate release streams for RHAIIS in our registry.redhat.io.

• Early Model Access Channel: This would be primarily used for day 0 model launches. This channel should have all the ProdSec and other exceptions in place so that we can quickly push the day 0 enablement image. The bits here will be built in midstream CI and pushed to this registry.
• Tech Preview Channel: This would be primarily used for releases that contain bits that are not fully stable yet. An example could be the LLM-D components that are still under active development but is required for an early launch.
• Fast/Stable Channel: This would be our regular monthly and Z-Stream releases for RHAIIS.

Product(s) associated:

RHAIIS

{}Goals:
Provide high-level goal statement with user context and expected user outcome(s) for this Feature

• We want to establish a standard playbook for delivering rapid preview releases while not introducing those into channels that customers would be using in production settings.

Requirements:
A list of specific needs, capabilities, or objectives that a Feature must deliver.

Done - Acceptance Criteria:
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

Use Cases - i.e. User Experience & Workflow:
Include use case diagrams, main success scenarios, alternative flow scenarios.

Out of Scope:
High-level list of items or personas that are out of scope.

Documentation Considerations :
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation.