Activate Milestone 5 release contract
This commit is contained in:
parent
6d06195950
commit
c3552f2328
2 changed files with 107 additions and 8 deletions
|
|
@ -15,6 +15,22 @@ deferred. Stable user and compatibility contracts still belong in dedicated docu
|
|||
- DocForge2 does not self-host during this program.
|
||||
- Release tags and Forgejo releases require Rob's explicit approval.
|
||||
|
||||
Milestone 5 was explicitly authorized on 2026-07-29 through the end of the roadmap, including
|
||||
evidence-based delegation and the milestone release actions frozen in `ACTIVE_SLICE.md`. That
|
||||
authorization does not widen the project, production-binding, or external-publication boundaries
|
||||
recorded there.
|
||||
|
||||
## Milestone 5 — active: stabilization and first DocForge2 release
|
||||
|
||||
Milestone 5 starts from the clean, merged, and pushed Milestone 4 closeout
|
||||
`6d06195950d33bcd2d712f8819bbfb3d6652ad03`. The candidate version is `1.4.0`, subject to the full
|
||||
release contract rather than version work alone.
|
||||
|
||||
The release work is evidence-first. Maintained compatibility, migration, recovery, concurrency,
|
||||
policy, projection, task-comparison, package, clone, browser, benchmark, and secret-scan gates must
|
||||
pass before documentation closeout, tag creation, or publication. `main` remains the Milestone 4
|
||||
baseline while implementation proceeds on `dev`.
|
||||
|
||||
## Milestone 0 — complete
|
||||
|
||||
Milestone 0 established the public successor, preserved the complete lineage and v1 tag, integrated
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue