Skip to content

docs: versioning & tracking convention (tags, milestones, labels) - #19

Merged
snese merged 1 commit into
mainfrom
docs/versioning-convention
Jul 15, 2026
Merged

docs: versioning & tracking convention (tags, milestones, labels)#19
snese merged 1 commit into
mainfrom
docs/versioning-convention

Conversation

@snese

@snese snese commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Records the tag / milestone / label scheme now in use so both human contributors and AI agents follow one source of truth.

  • New: docs/versioning-and-tracking.md — canonical convention:
    • Tags = delivered states, retroactive-friendly, 0.x (architecture still evolving), decoupled from the Helm chart version (tag v0.3.0 ships chart 1.4.0; Release notes must say so). Current line: v0.1.0 (KEDA era) → v0.2.0 (agent-sandbox runc) → v0.3.0 (gVisor + NetworkPolicy + scaling guard).
    • Milestones = planned phases, vMINOR — theme; maintenance phase precedes evolution phase; upstream-blocked work gets no milestone (uses upstream-dependency label) since a milestone implies schedulability.
    • Labels = orthogonal area/* classification + upstream-dependency.
  • AGENTS.md: pointer in the Conventions section (agent-facing).
  • CONTRIBUTING.md: pointer in the PR section (human-facing).

Documents the tags (v0.1.0–v0.3.0), milestones (v0.4/v0.5), and labels created for this repo today. Docs-only.

Canonical convention for how the sample records delivered states (git tags,
retroactive-friendly, 0.x, decoupled from the Helm chart version), planned
direction (milestones vMINOR — theme, upstream-gated work stays milestone-less
with the upstream-dependency label), and area classification (area/* labels).

Referenced from AGENTS.md (agent-facing) and CONTRIBUTING.md (human-facing)
so both developers and AI agents follow one source of truth.
@snese
snese merged commit 2cb44f7 into main Jul 15, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant