Cut and validate the first release candidate only after every milestone gate is satisfied.
Deliverables
Run full format/check/clippy/test/doc/fuzz-smoke/feature/platform/program suites and review all live/manual evidence.
Verify zero open milestone-owned implementation gaps, zero unimplemented shims, 100% API/test/program completeness, changelog/versioning, and signed/reproducible release artifacts as configured.
All release gates and audits are green with recorded evidence.
No critical/open compatibility defect is waived silently.
Release notes clearly state supported platforms/features/native prerequisites and any documented intentional API differences.
Prerequisite
All implementation and program milestones are complete with their fixed parity suites green.
Project constraints
The released implementation is entirely native Rust and must pass the explicit no-CLR/no-bridge artifact audit.
Do not weaken API coverage or semantic parity to satisfy hardening, performance, or packaging goals.
Preserve reproducible evidence, update release documentation, and keep all default/live destructive boundaries explicit.
## Objective
Cut and validate the first release candidate only after every milestone gate is satisfied.
## Deliverables
- Run full format/check/clippy/test/doc/fuzz-smoke/feature/platform/program suites and review all live/manual evidence.
- Verify zero open milestone-owned implementation gaps, zero unimplemented shims, 100% API/test/program completeness, changelog/versioning, and signed/reproducible release artifacts as configured.
- Perform clean-machine install, offline tools, fake-grid integration, and opt-in dedicated-account smoke.
## Validation
- All release gates and audits are green with recorded evidence.
- No critical/open compatibility defect is waived silently.
- Release notes clearly state supported platforms/features/native prerequisites and any documented intentional API differences.
## Prerequisite
All implementation and program milestones are complete with their fixed parity suites green.
## Project constraints
- The released implementation is entirely native Rust and must pass the explicit no-CLR/no-bridge artifact audit.
- Do not weaken API coverage or semantic parity to satisfy hardening, performance, or packaging goals.
- Preserve reproducible evidence, update release documentation, and keep all default/live destructive boundaries explicit.
hugo
added this to the 12 - Hardening and release milestone 2026-08-08 08:26:28 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Objective
Cut and validate the first release candidate only after every milestone gate is satisfied.
Deliverables
Validation
Prerequisite
All implementation and program milestones are complete with their fixed parity suites green.
Project constraints
all relevantg stuff implemented. closed for now.