Story: Open sprint 27

Table of Contents

This page documents a story in Sprint 27. It captures the goal, current status, acceptance criteria, and the tasks that compose it.

1. Goal

Sprint 27 exists as a proper agile artefact, with its mission set and wired into the version manifest and the agile index, and the project version carries 0.0.27, with the vcpkg submodule at latest.

2. Status

Field Value
State DONE
Parent sprint Sprint 27
Now Nothing.
Waiting on Nothing.
Next Nothing.
Last touched 2026-10-05

3. Acceptance

  • Sprint 27 has its mission and links Sprint 26 as Previous.
  • The version manifest lists Sprint 27 and the agile index names it as the current sprint.
  • The project version is 0.0.27 across the six recipe files, and the vcpkg submodule tracks latest.

4. Tasks

Task State Start End Description
Open sprint 27 DONE 2026-10-05 2026-10-05 Scaffold sprint 27, set its mission, wire the version manifest and the agile index.
Bump project version to 0.0.27 for sprint 27 DONE 2026-10-05 2026-10-05 Bump the project version from 0.0.26 to 0.0.27 across the build files and badges, and update the vcpkg submodule to latest.
Promote the carried stories into sprint 27 DONE 2026-10-05 2026-10-05 Move the fifteen stories carried from sprint 26 into sprint 27 and promote the retire-or-reset capture into a story, recording the sprint's scope.

5. Decisions

6. Out of scope

7. Result

Sprint 27 is open with its mission: finish the UX pass. No story carried over from sprint 26: its close resolved every story, and the nineteen unfinished ones wait in the product backlog inbox for sprint 27 planning. The version bump to 0.0.27 and the vcpkg update land with this same change, unlike sprint 26, where both were missed at the opening and patched at the close.

Planning followed the same day: sixteen of the carried stories joined the sprint (PR #2661) — the five mission stories, the five in flight and the six with work started. The rest stay in the inbox.

Emacs 29.3 (Org mode 9.6.15)