Repository navigation
docs: distribution status, post-1.0 readiness update, and the outlook - #19
Merged
Merged
Conversation
Ship-readiness: mark 1.0 released, record the hardening PR #15 and the eager implementation (PRs #16/#18) with the measured numbers, resolve the FLAG_EAGER hygiene item (the bit is real now: opt-in offer, mirrored only on the receiver's own opt-in), add the eager row to the gap table, and close the 'order to 1.0' list. New 'Outlook' section: what might come, ranked, each item a hypothesis to be decided on data (real-WAN measurement; D7 flaw-2 retry shape; macOS legs + Homebrew tap on first macOS demand; directory-mtime fast path needing a bench cell first; cross-tree index snapshot as the one real wire-feature candidate), and what deliberately won't be built (daemon, cloud remotes, xattrs/hardlinks, GUI, config) - the product is the small portable executable. README: version badge 0.8.0 -> 1.0.0 plus crates.io/docs.rs badges; install section states the honest package-manager status (winget/brew not set up; artifacts already shaped for both); roadmap gains the post-1.0 entries (hardening, eager single-file + tree).
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
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
Docs-only PR closing the last two phases of this round: distribution status and the outlook.
evaluation/ship-readiness.md: 1.0 marked released; hardening (PR test: pin the 1.0 hardening claims in CI (long paths, dry-run E2E, dir fsync) #15) and eager (PRs feat(protocol): eager diff mode (D8, §9.2) — stream DATA during the scan #16/feat(protocol): eager diff in tree sessions (D8, §16.11) #18) recorded with the measured numbers; the FLAG_EAGER hygiene item resolved (the bit is real: opt-in offer, mirrored only on the receiver's own opt-in, loud single-file decline, lazy tree fallback); eager added to the gap table; new Outlook section — ranked, data-gated candidates (real-WAN run, D7 flaw-2 retry shape, macOS legs + brew tap on demand, directory-mtime fast path behind a bench cell, cross-tree index snapshot as the one real wire-feature candidate) and the deliberate non-list (daemon, cloud, xattrs, GUI, config).No code changes
Everything here is documentation of verified state. Gates ran green on the tree (fmt, clippy
-D warnings, full suite) before this commit.