Release v0.2.0

Title: Desktop reference app

Status: Completed

Milestone: V0 software companion foundation

Version architecture: Architecture for v0.2.0

Archived records

RecordSource at rollover
Evidencerelease gate output and support evidence
Epicsdocs/02-epics.md
PBIsdocs/03-pbis.md
Progressdocs/progress.md
Bugsdocs/bugs.md
Known limitationsdocs/known-limitations.md

The release delivered nine epics, E08 through E16, and twenty-nine PBIs, PBI-035 through PBI-063. The bug register closed empty. Twelve limitations were recorded across the project, of which LIM-004, LIM-007, and LIM-009 were resolved during the release and remain only in this archive, and nine open limitations carry forward.

Identifier continuity

Identifiers do not restart after this release. The next active epic, PBI, bug, and ADR identifiers continue from the highest identifiers used before or during this release.

SequenceHighest used by v0.2.0Next identifier
EpicE16E17
PBIPBI-063PBI-064
Bugnone usedBUG-001
LimitationLIM-012LIM-013
ADRADR-007ADR-008

Release evidence

Evidence for the release claims is recorded in evidence.md and in section 10.5 of the version architecture. The verified toolchain is recorded in both places. The exit criteria are ticked in section 5.4 of the milestones document.

Notes

  • ADRs remain in docs/adr/. ADR-006 and ADR-007 were accepted during this release.
  • Version architecture remains in docs/arch/arch-v0.2.0.md.
  • Active planning continues in the root planning documents, which continue at E17 and PBI-064.
  • These files are historical records. Edit them only under the rules in section 9 of the release process.
  • The archived files keep their rollover content unchanged. Only their relative link paths were re-pointed with ../../ so they resolve from this directory, which section 9 permits as a broken link fix.
  • No git tag or frozen branch was created when this archive was written. Tagging v0.2.0 and creating release-v0.2.0 remain maintainer steps under section 7 of the release process.