Story: Sprint 24 closure: release notes and demo
Table of Contents
This page documents a story in Sprint 24. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Own the final steps of sprint closure: release notes summarising what shipped, illustrative screenshots captured through a real QA test scenario (not ad hoc), and the retrospective.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 24 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-08-03 |
Acceptance
- Release notes are generated and linked from the sprint's Status table. A test scenario captures screenshots suitable for illustrating the release notes. The sprint's Retrospective section is filled.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Write sprint 24 release notes | DONE | 2026-08-03 | 2026-08-03 | Generate release notes via compass add release_notes, populate from PR data and closed tasks' Result sections, and capture illustrative screenshots via a QA test scenario. |
| Fix unsubstituted {nats_wire_format} placeholder in systemd unit generator | DONE | 2026-08-03 | 2026-08-03 | systemd_generate.py substituted {nats_url}/{nats_prefix}/{nats_tls_args} but never {nats_wire_format}, so every service with a custom args_template (http.server, telemetry, ore.service, wt.service, all 5 compute.wrapper replicas) passed the literal string '{nats_wire_format}' to –nats-wire-format and crashed on every start. Found while starting services to run the release-notes screenshot scenario. |
Decisions
Out of scope
Result
Release notes generated (PR data + closed tasks' Result sections), illustrative screenshots captured (holiday-aware date picker, v0.0.24 hero shot), a broken-link bug in the shared exporter fixed and shipped to every future sprint's release notes, the retrospective written into sprint.org (condensed from the release notes' Post Mortem), tag v0.0.24 signed and pushed, and the draft GitHub release ("Capunda") published with corrected content. The still-open FX Spot Monitor wire-codec root-cause investigation was split into Find root cause of FX Spot Monitor wire-codec decode mismatch in sprint 25 rather than carried here as unfinished work.