Feature Overview (mandatory - Complete while in New status)
We use gitlab’s package registry to host our wheel artifacts today. This choice was expedient at the time, but we are reaching the limit of the features the tool can provide. We know we need to move to pulp registries for integration with Konflux anyway, but we also recently discovered that gitlab.com configures its package registry to “read through” to pypi.org when packages are missing, so we are exposed to potential security issues as a result.

Goals (mandatory - Complete while in New status)

• Move all wheel hosting for RHAIIS, RHEL AI, and RHOAI for 3.0 onwards to pulp.
• Ensure management of the repo for new collection versions is automated as part of the wheel build pipeline – consuming teams should not need to set up new infrastructure before changing the version number in a branch.
• Ensure creation of new repos is automated via our infrastructure repository – making new pulp repos may need higher privileges than updating them for release versions.

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):
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
…
<your text here>

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope _{}(Initial completion while in Refinement status):{_}
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations _{}(Initial completion while in Refinement status):{_}
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..
<your text here>

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.

• …