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

40
docs/MILESTONE_5_CLOSEOUT.md
View file

@ -1,15 +1,15 @@
# Milestone 5 release-candidate closeout
# Milestone 5 closeout
## Outcome
DocForge `1.4.0` has reached its documentation closeout candidate. Compatibility, migration,
DocForge `1.4.0` completes the first DocForge2 successor release. Compatibility, migration,
determinism, concurrency, recovery, policy, projection isolation, accessibility, performance,
adoption, artifact reproducibility, and representative real-task evidence are maintained and
passing.
This is not the final publication record. Milestone 5 remains active, and DocForge `1.0.0` remains
the latest published stable release, until the documentation-bearing commit passes its final
fresh-clone gate and the annotated `v1.4.0` tag and Forgejo release are verified.
The documentation-bearing candidate passed its complete local release gate. Its final
documentation-only descendant passes the anonymous exact-commit clone gate and is identified by
the annotated `v1.4.0` tag and public Forgejo release.
## Candidate lineage
@ -21,11 +21,11 @@ fresh-clone gate and the annotated `v1.4.0` tag and Forgejo release are verified
`97f3b6b1ae303c972387508557a3d54ea621a702`.
- Maintained aggregate recovery proof:
`2b98059b44f4d46b4d4cce776f163e893c647c76`.
- Intended release version and tag: `1.4.0` and `v1.4.0`.
- Release version and tag: `1.4.0` and `v1.4.0`.
- Publication channel: public Forgejo release only.
The tag does not exist yet. It must resolve to the final documentation-bearing descendant of this
lineage, never to the earlier executable-only commit.
The tag resolves to the final documentation-bearing descendant of this lineage, never to the
earlier executable-only commit.
## Closed release evidence
@ -34,7 +34,7 @@ The clean executable release gate passed:
- Formatting, Python and web lint, strict types, compilation, lock, dependency, package-build,
generated-reference, and documentation checks.
- 142 contract tests plus 272 subtests.
- 371 complete tests plus 419 subtests.
- 378 complete tests plus 422 subtests.
- Three interactive accessibility flows.
- 116 compatibility tests plus 263 subtests.
- 29 concurrency tests plus 2 subtests.
@ -43,8 +43,8 @@ The clean executable release gate passed:
- Gitleaks scans of reachable history and the candidate directory with no findings.
- Full maintained Milestone 0, 1, 2, 3, and 4 benchmarks.
The later proof-only recovery commit adds four maintained tests. The aggregate recovery gate now
passes 72 tests plus 62 subtests. The final fresh clone owns the final complete-suite total.
The proof-only recovery commit adds four maintained tests. The aggregate recovery gate passes 72
tests plus 62 subtests.
Detailed migration identities, artifact evidence, recovery boundaries, and task measurements are
in the [Milestone 5 baseline](MILESTONE_5_BASELINE.md).
@ -86,16 +86,12 @@ smaller, so no universal response-size advantage is claimed.
change belongs to this release.
- No PyPI publication belongs to this release.
## Publication still pending
## Publication
The remaining sequence is exact:
`main`, `dev`, `origin/main`, and `origin/dev` resolve to the exact documentation-bearing release
commit. An anonymous HTTPS clone of that commit verifies the frozen annotated `v1.0.0` migration
tag and repeats the complete release gate before `v1.4.0` is created.
1. Commit this coherent documentation closeout on the verified candidate lineage.
2. Run documentation-only checks and confirm the final worktree contains no unrelated changes.
3. Merge and push the final candidate so `main`, `dev`, `origin/main`, and `origin/dev` agree.
4. Run the complete fresh-clone release rehearsal at that exact remote commit.
5. Build the final artifacts and checksum manifest from the verified commit.
6. Create and push one annotated `v1.4.0` tag at that commit.
7. Publish and verify the Forgejo release and attached artifacts.
Until all seven steps succeed, the milestone status is release candidate rather than complete.
The public Forgejo release attaches the reproducible wheel, source distribution, and
machine-readable release-identity evidence containing their exact SHA-256 checksums. No PyPI
publication, production binding change, or legacy-repository mutation is part of this release.