Repository navigation
Commit a18d228
committed
docs(roadmap): align near-term plan with committed capacity
Separate commitments from direction. Deliverables through 2027 Q1
have owners, issues and capacity behind them; everything later is
stated as intent and restated each quarter. A public roadmap that
misses its own dates costs more at a Graduation review than one
that says plainly which half is which.
Refresh the current-state snapshot to August and mirror the open
items on Project V2 #1, which had drifted: backups for managed
apps, OpenBao/ESO, kstatus, the unified TLS model, diff-driven
E2E and the Cilium tracking epic were all in flight and unlisted.
Put the real near-term work into the 2026 quarters: the service
exposure contract, per-application TLS, tenant quotas, database
autoscaling, and a reproducible performance benchmark. Mark the
E2E pipeline as the gating item it is — while it is red, releases
and large PRs queue behind it.
Govern blockstor and cozyplane inside Cozystack instead of filing
separate foundation applications, and gate the LINSTOR deprecation
on production mileage plus a working reverse migration.
Form SIGs in three waves as chairs and recurring work appear,
rather than standing up eleven calendars at once. Scope the
near-term AI work to releasing cozyllm and documenting the
existing GPU path, and require the dashboard assistant to run
self-hosted, since regulated adopters cannot send cluster state
to a hosted API.
Drop the reference to the maintainer-only scanner repository and
describe the process instead.
Assisted-By: Claude
Signed-off-by: Andrei Kvapil <[email protected]>1 parent 4cba87d commit a18d228
1 file changed
Lines changed: 46 additions & 31 deletions
0 commit comments