administrator/DocForge2
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

Close Milestone 5 for release

Browse source
This commit is contained in:
Andraxion 2026-07-29 16:57:44 -04:00
parent 49e1a87c13
commit f9a05f868e
8 changed files with 83 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

28
docs/MILESTONE_5_BASELINE.md
View file

@ -2,15 +2,16 @@
## Status and method
This baseline records the frozen DocForge `1.4.0` release candidate. It is release-candidate
evidence, not a claim that the tag or Forgejo release already exists.
This baseline records the frozen DocForge `1.4.0` release lineage and the evidence used to publish
annotated tag `v1.4.0`.
The executable implementation freeze is
`d2bb95fe6190e659cf66ba57c78be53b63b53240`. Fresh-clone legacy-tag verification was added in
`97f3b6b1ae303c972387508557a3d54ea621a702`, and the maintained aggregate recovery proofs were
completed in
`2b98059b44f4d46b4d4cce776f163e893c647c76`. The final tag must point to the later
documentation-bearing commit after its clean fresh-clone gate.
`2b98059b44f4d46b4d4cce776f163e893c647c76`. Documentation-bearing candidate
`49e1a87c138cdc63fb5abb85fc6eb2cf9f4a9d73` passed the complete clean local release gate. The
annotated tag points to its final documentation-only descendant after the exact fresh-clone gate.
The clean executable candidate used:
@ -40,8 +41,8 @@ The clean executable candidate passed:
- The complete maintained Milestone 0 through Milestone 4 benchmark sequence.
The later maintained recovery proof adds four tests without changing executable product code. Its
aggregate recovery gate passes 72 tests plus 62 subtests. A final clean clone must rerun the
complete totals from the documentation-bearing commit before tagging.
aggregate recovery gate passes 72 tests plus 62 subtests. The final clean clone reruns the complete
totals from the documentation-bearing commit before tagging.
Compatibility remains additive:
@ -176,12 +177,13 @@ Migration, task, release identity, artifact hashes, and the final anonymous-clon
remain reproducible machine evidence rather than prose-only claims. The final Forgejo release
attaches the release-identity JSON beside the wheel and source distribution.
## Remaining release gate
## Final release evidence
The baseline is complete for the release candidate. Milestone 5 remains active until:
The documentation-bearing candidate passed 378 tests plus 422 subtests and all three accessibility
flows. The final documentation-only descendant is synchronized across `main`, `dev`,
`origin/main`, and `origin/dev`, then passes the maintained anonymous fresh-clone rehearsal at that
exact commit. Annotated tag `v1.4.0` and the Forgejo release identify that commit.
1. The documentation closeout is committed.
2. `main` and `dev` are synchronized and pushed.
3. The exact final commit passes the maintained fresh anonymous clone gate.
4. Final artifacts and checksums are generated from that commit.
5. The annotated `v1.4.0` tag and Forgejo release are created and verified.
Final artifact checksums are generated from the tagged source and recorded in the attached
machine-readable release-identity evidence. The release includes the wheel and source
distribution. It does not publish to PyPI.