Milestones
List view
Release gates from the operational/usability review of PR #1: published user-installable packages, state-preserving upgrade and rollback, and actionable interrupted-work recovery. Existing implementation issues retain their current milestones and are linked by the release checklist. No release date is implied.
No due date•1/2 issues closedDurable outcomes, cancellation, recovery, output and resource conservation. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•48/48 issues closedUser and node identity, authorization and limits on untrusted work. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•17/21 issues closedConsistent traffic policy, aggregate budgets and evidence-backed packet attribution. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•12/14 issues closedConfiguration, diagnostics, services, backups, upgrades, observability and reproducible releases. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•56/58 issues closedVersioned interfaces, usable clients and reproducible examples. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•19/21 issues closedMaintainer responsibilities, support policy, contribution documentation and publication preparation. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•21/23 issues closedPortable results and controlled, reproducible measurement experiments. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•9/9 issues closedOptional credits and monetary settlement. Real monetary activation is not part of the local alpha. Implementation and validation currently use local development and supported Linux CI. Dates and ownership are assigned during prioritization; this milestone is not a calendar commitment.
No due date•13/13 issues closed