Milestones

Table of Contents

Summary

A milestone is the named major release target that a version series works towards — the major release that closes one series and opens the next. Milestones own the what and why: identity, theme, mission, and definition of done. Versions own the how and when: the release series, sprints, and in-progress builds. The two are distinct documents so neither duplicates the other.

Milestones vs versions

Concept Owns Example
Version Release series, sprints, in-progress builds Version 0 (0.0.x builds)
Milestone Identity, theme, mission, DoD, time horizon Milestone v1.0

A version does not carry a mission statement of its own; it points to its target milestone instead. When the milestone's definition of done is met, the version closes and the software cuts the milestone release (e.g. 1.0.0). Work then moves to the next version series.

Catalogue

Milestone Theme Version series Time horizon Status
v1.0 — Static World Static world Version 0 (0.x.x) ~6 months IN PROGRESS
v2.0 — Dynamic World Dynamic world Version 1 (1.x.x) ~18 months PLANNED

See also

  • Roadmap — the user-facing narrative of where the product is going.
  • Versions — the version series that do the work.
  • Agile — entry point to the agile information architecture.

Emacs 29.1 (Org mode 9.6.6)