Skip to content

Release record R3 + R4: outcomes, readiness, changelog, planning, calendar, Autoland eligibility - #93

Merged
jfillman merged 1 commit into
mainfrom
release-record-r3-r4
Oct 14, 2026
Merged

jfillman merged 1 commit into
mainfrom
release-record-r3-r4

Conversation

@jfillman

Copy link
Copy Markdown
Owner

What

R3 and R4 of the Release Record work. This needs jfillman/backstage#138.

R3: learn from what shipped

  • Outcome on every record. The possible outcomes are:

    • clean
    • rolled back (names the release it rolled back to, and the reason)
    • replaced before healthy
    • stopped before production
    • baking · day N of 7 (while the release is still in its bake window)

    The outcome shows in the list, in a new Outcome panel on the opened record, and in Compare.

  • The score is now "readiness": how ready the release was when it shipped. The constant "+5, no incidents" is gone, so every score drops by 5. The outcome sits beside the score.

  • Changelog view: every release's notes, newest first.

  • GitHub Release opt-in: a new checkbox in the draft. The record links the release once it's published.

R4: plan and share

  • Draft target date and milestone:
    • A "Planned" list of the milestone's open issues.
    • Two new readiness checks: Target date (shown as a to-do when late) and Planned issues closed.
  • Jira links (when tower.jira.baseUrl is set). Linked issues show their own labels.
  • Ops Wall: Release calendar panel.
  • Autoland eligibility under the mode bar. It is display only: tests, canary, production metrics, a clean history and readiness.
  • Activity: the release-record and release-signoff topics now have a category and label. The R2 sign-off alert was being filtered out of the feed.

Verified

  • tsc, lint and yarn ratchet are clean. 806/806 tests pass, including new tests for outcomes, the changelog, Autoland eligibility, the calendar panel, Jira links, planned scope and the target date.
  • Live in the local harness against the real clusters:
    • On boarding-api (now Hand-flown, with your draft and PR Release record: cloud Flight releases via pin PR; layout option A #41 open): the mode bar, Autoland eligibility (1 of 5), the draft card and readiness all render. Readiness is 7 of 9, including notes, owner and sign-off.
    • The Changelog lists all 8 releases.
    • The Ops Wall Release calendar shows every app's next release, and boarding-api shows its owner, 4 notes and "→ staging".
    • No existing record shows an outcome. That's correct: their tracking records predate ADR-0021 phase 4 and carry no image to match.

🤖 Generated with Claude Code

…endar, Autoland eligibility

R3:
- Outcome: every record shows what happened after it shipped (clean, rolled
  back, replaced before healthy, stopped before production, or baking day N of
  7), in the list, the open record (an Outcome panel naming the release that
  replaced it or the reason for a rollback) and Compare. A rolled-back record
  reads rolled back.
- The score is now "readiness": how ready the release was when it shipped. The
  constant "+5, no incidents" is gone (Tower never tracked incidents);
  outcomes sit beside the score, not in it.
- Changelog view: every release's notes, newest first.
- Draft: "Publish a GitHub Release" opt-in; the record links it.

R4:
- Draft: target date and milestone. The card lists the milestone's open issues
  as Planned; readiness gains Target date and Planned issues closed.
- Jira keys in PR titles, bodies and branches link out when tower.jira.baseUrl
  is set; linked issues show their own labels (#12, owner/repo#5, BAG-12).
- Ops Wall: Release calendar panel (next release by name, target date, owner,
  notes, in flight, last release and its outcome).
- Autoland eligibility under the mode bar (display only).
- Activity: release-record and release-signoff notifications have a category
  and label (the R2 sign-off alert was being filtered out).

Needs the matching backstage routes. Docs: docs/release-records.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jfillman
jfillman merged commit 645dcae into main Oct 14, 2026
1 check passed
@jfillman
jfillman deleted the release-record-r3-r4 branch October 14, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant