Release v0.3.0
Title: Embedded firmware foundation and project UX
Status: Completed
Milestone: V0 software companion foundation
Version architecture: Architecture for v0.3.0
Archived records
| Record | Source at rollover |
|---|---|
| Evidence | release gate output and support evidence |
| Epics | docs/02-epics.md |
| PBIs | docs/03-pbis.md |
| Progress | docs/progress.md |
| Bugs | docs/bugs.md |
| Known limitations | docs/known-limitations.md |
The release delivered seven epics, E17 through E23, and twenty-two PBIs, PBI-064 through
PBI-085. The bug register closed empty again. LIM-005 and LIM-010 were resolved during the
release and remain only in this archive, LIM-003 and LIM-012 were narrowed, LIM-013 was
opened, and eight 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.
| Sequence | Highest used by v0.3.0 | Next identifier |
|---|---|---|
| Epic | E23 | E24 |
| PBI | PBI-085 | PBI-086 |
| Bug | none used | BUG-001 |
| Limitation | LIM-013 | LIM-014 |
| ADR | ADR-011 | ADR-012 |
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 6.4 of the milestones document.
The hosted claim is build and runtime evidence on Linux under GCC and Clang. The embedded claim is
cross-compile evidence for the classic LILYGO T-Display as ESP-IDF esp32, and it is not a hardware
runtime claim.
Notes
- ADRs remain in
docs/adr/.ADR-008throughADR-011were accepted during this release. - Version architecture remains in
docs/arch/arch-v0.3.0.md. - Active planning continues in the root planning documents, which continue at
E24andPBI-086. - 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 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.3.0and creatingrelease-v0.3.0remain maintainer steps under section 7 of the release process.