Repository navigation
Release record R3 + R4: outcomes, readiness, changelog, planning, calendar, Autoland eligibility - #93
Merged
Merged
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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
tower.jira.baseUrlis set). Linked issues show their own labels.release-recordandrelease-signofftopics now have a category and label. The R2 sign-off alert was being filtered out of the feed.Verified
tsc, lint andyarn ratchetare 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.🤖 Generated with Claude Code