What
Tracking epic to coordinate v1.0 API stabilization across all 8 kcenon ecosystem repositories. This epic tracks the remaining work for stable v1.0 releases.
State refreshed on 2026-05-10 by #682. The original body claimed "all 8 repositories at version 0.x.x" — this is no longer accurate. The audit is recorded as a comment on #682 with the full state matrix.
Why
- Some libraries have shipped v1.0 (
thread_system, container_system, database_system); others remain pre-1.0 or have incomplete v1.0 work
- Downstream consumers (especially
pacs_system) need stable APIs to build production systems
- Coordinated release ensures dependency compatibility across the ecosystem
- Priority: Medium — foundational work for long-term ecosystem health
Where
Current Version Status (audited 2026-05-10)
| Repository |
Latest Tag |
CMake VERSION |
CHANGELOG v1.0.0 |
v1.0 Epic |
State |
| common_system |
v0.2.0 |
1.0.0 |
Yes (2026-04-13) |
#640 |
CLOSED — release tag publication pending |
| thread_system |
v1.0.0 |
1.0.0 |
Yes (2026-04-15) |
#670 |
CLOSED — v1.0 shipped |
| container_system |
v1.0.0 |
1.0.0 |
Yes (2026-04-16) |
#512 |
CLOSED — v1.0 shipped |
| logger_system |
v0.1.3 |
0.1.3 |
No |
#604 |
REOPENED — premature close, v1.0 work incomplete |
| monitoring_system |
v0.1.0 |
0.1.0 |
No |
#667 |
REOPENED — premature close, v1.0 work incomplete |
| database_system |
v1.0.0 |
1.0.0 |
Yes (2026-04-16) |
#564 |
CLOSED — v1.0 shipped |
| network_system |
v0.1.1 |
0.1.1 |
No |
#964 |
OPEN |
| pacs_system |
v0.1.0 |
0.1.0 |
No |
#1095 |
OPEN |
How
v1.0 Readiness Criteria (per repository)
Proposed Release Order (bottom-up by tier)
common_system v1.0 — VERSION/CHANGELOG ready; publish v1.0.0 git tag and GitHub release
thread_system v1.0 + container_system v1.0 — Tier 1 shipped
- logger_system v1.0 — complete
[Unreleased] BREAKING entry, bump VERSION, tag and release
- monitoring_system v1.0 +
database_system v1.0 — bump monitoring_system VERSION and release; database_system shipped
- network_system v1.0 — Tier 4 (requires test coverage + Result migration first)
- pacs_system v1.0 — Tier 5 (after all dependencies are stable)
Remaining Blockers for v1.0
What
Tracking epic to coordinate v1.0 API stabilization across all 8 kcenon ecosystem repositories. This epic tracks the remaining work for stable v1.0 releases.
Why
thread_system,container_system,database_system); others remain pre-1.0 or have incomplete v1.0 workpacs_system) need stable APIs to build production systemsWhere
Current Version Status (audited 2026-05-10)
v0.2.01.0.0v1.0.01.0.0v1.0.01.0.0v0.1.30.1.3v0.1.00.1.0v1.0.01.0.0v0.1.10.1.1v0.1.00.1.0How
v1.0 Readiness Criteria (per repository)
throwin public APIs*_system::*_system)Proposed Release Order (bottom-up by tier)
common_system v1.0— VERSION/CHANGELOG ready; publishv1.0.0git tag and GitHub releasethread_system v1.0+container_system v1.0— Tier 1 shipped[Unreleased]BREAKING entry, bump VERSION, tag and releasedatabase_system v1.0— bump monitoring_system VERSION and release; database_system shippedRemaining Blockers for v1.0
v1.0.0git tag and GitHub release (in-repo metadata already at 1.0.0)[Unreleased](#534), bump VERSION to 1.0.0, tag, release (epic #604)[1.0.0]section, tag, release (epic #667)CMake package name migrationshipped in v1.0.0