Feature Overview:

We need to keep track of why we are building the packages we have in the package index so that we can know who to contact if there are issues and so we know when they are no longer needed.

Product(s) associated:

RHAIIS:
RHEL AI:
RHOAI: yes

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

• For each package we build, we need to track metadata about why we are building it so we can understand when to stop, who to go to if we have issues, etc.

Requirements:

We want teams to provide us with the top level dependencies they need and let us work out the build and installation dependencies.

• Metadata to track
  • The team(s) requesting the package. We will look to them for advice about version selection, CVE resolution, deprecation, etc.
  • The original date the package is requested.
  • The Jira ticket from the original request.
  • Any dates when other teams also start explicitly requesting the package.
  • The Jira tickets for additional requests.
  • The minimum version to build, if any.
  • The AIPCC team involved in the build, in case issues arise in the future.
  • Comments about why the package is needed.
• We need to track this metadata consistently in one place. For packages that require customization, we will have that information in the builder repo settings file metadata but for packages that do not require customization, we will not have entries in the builder file.
• We need to be able to display this information in the release dashboard.

Done - Acceptance Criteria:

Anyone can go to the release dashboard and find the package request data for a package by searching for its name. The dashboard shows the information described in the requirements above, as well as the version(s) of the package in the index at the time of the query.

Use Cases - i.e. User Experience & Workflow:

As a member of a component team, I want to understand which version of the package I have requested is being published in the package index.

As a member of a component team, I want to register that I need a package that has not been built before.

As a member of a component team, I want to register that I need a package that has been built based on a request from someone else.

As a member of the AIPCC team, I want to see how long we have been building a particular package and why.

Out of Scope:

We will not redesign the package build request process as part of this ticket.

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.