Feature Overview:

We build vllm and llama-stack from mirrors managed by component teams in their midstream. We build using tags those teams apply, using versions that may not match the upstream versions. We need to standardize the way we define those tags so we can have a single implementation of the code in our code base, document how to apply the tags, and work consistently with all teams.

Product(s) associated:

RHAIIS: Yes
RHEL AI: Yes
RHOAI: Yes

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

• Define a consistent midstream tagging pattern so we can standardize our tooling downstream and in the midstream.

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

1. We want a tagging pattern that clearly differentiates tags from upstream version tags. We may want to build upstream versions sometimes, but more often for these packages we will want to build the from the commits that the component team selects.
2. We want a tagging pattern that works across all packages in the Python ecosystem, so that we do not have to invent a new system for each package.
3. We want a tagging pattern that allows us to build different commits for different accelerated builds.
4. We want this process to be simple so everyone can understand it, the implementation is easy to get right, and so we can continue to use as many of our other standard tools (fromager, renovate, pip, etc.) as possible.

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.