Feat: Release Cutting Go/No-Go Decision Automation

[knabben]

Description

The handbook requires giving a "Go" or "No-Go" signal to the release team when a release is being cut. Currently, signalhound does not support release readiness evaluation.

Requirements

• Evaluate release readiness based on dashboard health
• Generate Go/No-Go recommendation
• Consider blocking failures, flake rates, and informing issues
• Generate summary report for release cutting decision
• Support release cutting workflow

Acceptance Criteria

• Release readiness is evaluated from dashboard data
• Go/No-Go recommendation is generated
• Decision logic matches handbook criteria
• Summary report is generated for release team
• Report includes blocking failures, flakes, and issues
• Unit tests for decision logic
• Integration tests with dashboard data

Implementation Notes

• Count blocking failures and flakes
• Check informing dashboard issues
• Apply decision criteria from handbook
• Generate markdown report with recommendation
• Support --release-cut command

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tico88612]

/remove-lifecycle stale
/triage accepted