Task: Write sprint 26 release notes
Table of Contents
This page documents a task in the Sprint 26 closure: story cleanup and reset for sprint 27 story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
Sprint 26 has release notes that describe what shipped, what was carried at close and why, and a post mortem. The notes ship as the body of the v0.0.26 draft GitHub release.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Sprint 26 closure: story cleanup and reset for sprint 27 |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-05 |
3. Acceptance
release_notes.orghas no placeholder left, and every claim matches the record.- The four charts are rendered at the sprint root.
release_notes.mdis exported for the draft GitHub release.
4. Result
The release notes are written, linked and exported. They are generated
from the 516 pull requests merged since the v0.0.25 tag (2026-09-23 to
2026-10-05) and then edited: the summary blurb, the highlights, the
ores.cli known-issue reason and the next-sprint line state the sprint's
real record, and the twenty abandoned stories the generator listed as
key improvements are pruned from that section. The sprint's status
table and retrospective link the notes by ID. The four charts — PRs
and commits per day, daily line churn, PR cycle time and cumulative
stories done — are rendered at the sprint root over the sprint's real
window, 2026-09-23 to 2026-10-05, since the status table keeps the
planned end date. release_notes.md is exported for the v0.0.26 draft
GitHub release, which is created after the merge.