docs: RELEASING.md checklist + reconcile PRD §11–§12 v0.1 status#38
Merged
Conversation
Stages the v0.1.0 release so cutting the tag is one mechanical pass once the operational gates pass. No version bump or tag yet. - RELEASING.md (new): the cut-v0.1.0 checklist — operational gates first (≥24h EncString fuzz soak, a live PQC handshake, the two-week daily-driver), then the mechanical steps (version 0.0.1→0.1.0, CHANGELOG [Unreleased]→[0.1.0]+date, CI-exact gates, --version check, PROJECTS refresh, signed annotated `v0.1.0` tag). Notes the Personal/Hobby posture. - PRD.md: §11 success metrics annotated done vs operational (+ a "code complete" status line); §12 milestone table gains a Status column (M0–M5 ✅; M6 vim+accessibility done / theme loader out of scope; M7 PQC + hardening + fuzz harness done, tag pending the operational gates). Masthead Last-updated bumped. - CHANGELOG entry. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Stages the
v0.1.0release. All code-side work has landed; what remains is maintainer-operational (the ≥24h EncString fuzz soak, a live PQC handshake test, and the two-week daily-driver attestation). This adds a checklist so cutting the tag later is one mechanical pass, and reconciles the PRD's v0.1 criteria to mark what's done vs. operational. Docs only — no version bump or tag.How
RELEASING.md(new) — the cut-v0.1.0checklist: operational gates first (fuzz soak / live PQC / daily-driver, cross-referencingdocs/fuzzing.md,docs/pqc.md,docs/m2-vaultwarden.md), then the mechanical steps (version0.0.1→0.1.0, CHANGELOG[Unreleased]→[0.1.0] - <date>, the CI-exact gate set,--versioncheck,projects/PROJECTS.mdrefresh, signed annotatedv0.1.0tag). Notes the Personal/Hobby posture (no SLA/semver promise).PRD.md— §11 success metrics annotated done (✅) vs operational (⏳) with a "code complete (2026-06-16)" status line; §12 milestone table gains a Status column (M0–M5 ✅; M6 vim + accessibility ✅, runtime theme loader out of scope; M7 PQC flag / hardening / fuzz harness ✅, tag pending the operational gates). MastheadLast updatedbumped.Verification
Docs-only:
cargo fmt --all -- --checkclean,cargo build --workspacegreen; clippy/test/deny/headless and the--versiongate are unaffected (no Rust or version change). SPDX header present on the new.md.Out of scope
The actual version bump /
[0.1.0]CHANGELOG cut /v0.1.0tag — the mechanical steps the new checklist drives, run once the operational gates pass.🤖 Generated with Claude Code