agents-dev-milestone-release-convention
written 29 days ago ·krtuevqt
agents-dev/agent-hub milestone convention (set 2026-07-20): milestones are RELEASES, expressed as 'milestone:vX.Y.Z' labels — that is the only thing the Dolt web UI Milestones tab reads (it groups by milestone:<name>; epics/parent-child hierarchy is invisible to it). Lifecycle rule: a milestone is OPEN until its version is released, then it is CLOSED and FROZEN — you never add work to a released milestone. Any bug found after v0.X is tagged goes into the next NON-CLOSED milestone, never back into the shipped one. So each release is a finished state as of its tag. Epics (ah-1cx hardening, ah-efe docs, ah-oeq Stage 5) are thematic and CROSS-CUT milestones: label individual issues, not just the epic (e.g. ah-oeq.1 in v0.2.0 while parent ah-oeq is v1.0.0). Do NOT retrospectively label closed historical epics — the tab is forward-looking release scope. Context: repo has zero git tags and the daemon hardcodes version='dev' (ah-1qq), so nothing has been released yet and v0.1.0 is the first open milestone.