• Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • MCP
    • None
    • MCP in RHDH: Upstream Contribution Lifecycle
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • RHDHPLAN-391 - [MCP] Strategy: Adopt Upstream MCP Actions & Establish 'Extras' Incubation Layer
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed

      EPIC Goal

      Develop processes for contributing MCP tools in Backstage as well as in the "extras" overlays in RHDH. Also identify 1.10 features that are delivering MCP features that can be upstreamed. 

      For MCP tools that are delivered under extras for some reason (e.g. if waiting on Backstage feedback, or PR reviews, or some other reason), develop a process to determine when those tools can be upstreamed and removed from the extras overlays (e.g. if the PR is merged and will be available upstream in the next version of Backstage RHDH pulls in). 

      Also, as part of this epic, look at the upstream spikes (e.g. audit logging) that were completed in 1.9 and see if there's any potential contributions we can provide back to Backstage.

      Background/Feature Origin

      As part of RHDHPLAN-391, while we're trying to prioritize contributions upstream for MCP tools in RHDH/Backstage, we are implementing an "extras" overlays for plugins that cannot be immediately upstreamed. As part of that, we need to determine a process for how these "extra" MCP tools can graduate out of the overlays. 

      Why is this important?

      By providing a way for MCP tools to graduate out of the extras overlays, this will ensure we keep upstream MCP tools a priority, and ensure we don't keep an ever-growing list of MCP tools downstream

      User Scenarios

      Dependencies (internal and external)

      Acceptance Criteria

       

      • Develop process for contributing MCP features to both upstream and -extras, as needed
      • Develop process for upstreaming eligible MCP tools from extras and removing the downstream parts
      • Identify eligible 1.10 MCP features for upstreaming (and any previous 1.9 upstream spikes)
        • Stretch: Implementation of upstream spikes from 1.9 (audit logging, event/notification integration)

      Release Enablement/Demo - Provide necessary release enablement details
      and documents

      DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
      Issue>

      DEV - Upstream documentation merged: <link to meaningful PR or GitHub
      Issue>

      DEV - Downstream build attached to advisory: <link to errata>

      QE - Test plans in Playwright: <link or reference to playwright>

      QE - Automated tests merged: <link or reference to automated tests>

      DOC - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              johnmcollier John Collier
              RHDH AI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: