mcpField
R
rhdh-release-schedule

rhdh-release-schedule

github.com/redhat-developerDevelopment1946 installsUpdated 1d ago
Repository

About rhdh-release-schedule

rhdh-release-schedule is a read-only skill for finding RHDH release milestone dates. It consults Jira for releases in progress and a schedule spreadsheet for later milestones, reporting the source for each date.

Key features

  1. 01Looks up dates in Jira or a schedule spreadsheet
  2. 02Identifies the source for each reported date
  3. 03Reports TBD dates without estimating
  4. 04Shows conflicting source dates side by side

Use cases

  1. 01Find the date of an RHDH release milestone
  2. 02Check dates for releases further in the future
  3. 03Compare conflicting dates from the two sources
  4. 04Confirm whether a version appears in either source

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/redhat-developer/rhdh-skills --skill rhdh-release-schedule

After installing, type/rhdh-release-schedulein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
scripts/
_jira.py
_support.py
jql-release.md
jql.py
release.py
rich_filter.py
slack_templates.py
slack-templates.md
workflows/
release-dates.md

Details

From the project README

RHDH release dates

Say when a milestone falls, and say which source said so. Read-only.

Route

Load workflows/release-dates.md. One workflow covers both sources: Jira for releases already in flight, the schedule spreadsheet for anything further out. Which one answers a given version is a lookup, not a decision the user makes.

Boundary with the neighbouring skills

  • What is still open against a release is /rhdh-release-status.
  • Drafting the Slack message that goes out at a freeze is /rhdh-release-announce, which pulls the date it needs itself.
  • The SoS check-in report for team leads is /rhdh-release-sos.
  • Which OCP, AKS, EKS, GKE, or PostgreSQL versions a release supports, and when they go end-of-life, is /rhdh-platform-lifecycle. Product lifecycle is not a release milestone.
  • Reading or editing the RHDHPLAN release Feature as a Jira issue is /rhdh-jira-api.
  • Ensuring the fix version for a release exists on RHIDP, RHDHPLAN, and RHDHBUGS is /rhdh-release-fixversions.

Completion

Complete when every date reported names its source — the Jira release issue key or the schedule spreadsheet tab — and dates the two sources disagree on are shown side by side rather than silently reconciled. A milestone the source records as TBD is reported as TBD, never estimated from the surrounding dates or from a previous release's spacing. When a version appears in neither source, say so and ask for the exact version string as it appears in the sheet.

Comments

Markdown supported