aboutsummaryrefslogtreecommitdiffstats
path: root/docs/development.md
Commit message (Collapse)AuthorAgeFilesLines
* scripts/wire-check: a swarm of the last release and this treetv2 days1-1/+17
| | | | | | | | | | | | | | | | Four nodes on this host over libp2p on loopback, two of a release tag's build and two of this tree's, in turns, each seeded with the one before. Where the two builds' wire versions meet, each node writes, and the check is that every node reads what each wrote and that none logs a peer of another wire version. Where they don't, that the tag's nodes log this tree's as such, so their operators know to upgrade. scripts/release runs it against the last release, after saying from the two builds' --version how the release upgrades: so a release that says it rolls out node by node has been seen to. docs/development.md says how a change to the wire format is made: a new version beside the ones spoken already, the older kept frozen.
* scripts/release: a release checked, said how it upgrades, committed and taggedtv2 days1-0/+29
| | | | | | | | | | | | | | | | | | | | | | | | Releases were made by hand: a commit, a tag, and whatever one remembered to check. `scripts/release [--dry-run] X.Y.Z` makes one: 1. the tree clean, notes under Unreleased in CHANGELOG.md, the version later than the last v* tag's; 2. the version set in Cargo.toml and Cargo.lock (and the --version example in operations.md), then `cargo quick`, `cargo sim` and scripts/federation-check, stopping at the first that fails and leaving the tree as it was; 3. this build's `continuum --version` against the last release's, built in a cache of its own: node by node where their wire versions meet and Automerge is the same, every node together where they don't share one, which from 1.0.0 on it refuses but in a major release; Automerge changed, no remake until every node runs it; 4. the Unreleased notes become the release's, headed by what it found; the commit `release X.Y.Z`, tagged vX.Y.Z with that, what the build speaks and knows, and the notes; and federation-<F>.<R> too where the build knows a later revision than the last release. It pushes nothing. With --dry-run it checks and prints what it would write. docs/development.md says how releases are made.
* federation: the feature, and the store's foldtv5 days1-10/+13
| | | | | | | | | | | | `federation`, a feature of its own, builds what `docs/federation.md` and `docs/store.md` design, stage by stage; without it continuum builds and behaves as it does. The aliases build with it, and `docs/development.md` says so. Its first part is the store's: an event's ID, the SHA-256 of its bytes written as 64 lower-case hex digits and read back only so, and the `Fold` trait as `docs/store.md` gives it. The trait reads a checkpoint's parts too, the heads it was built at and the events it keeps, which a node taking a pinned checkpoint needs; the design names it. Nothing uses either yet, but a test.
* bench: what screening costs while catching uptv13 days1-2/+2
| | | | | | | | | | | Review 2, N7, measured first: a node whose document has no policy (a joiner's empty one) applies what it receives unjudged. Screening it too would cost finding every change's paths and judging it. bench_screening takes 1 000, 10 000 and 100 000 changes into an empty document, as one delta brings them: unjudged, as Automerge applies them, against screened (access::screen::apply), with no policy in them (each passes, read at its dependencies, after its paths were found) and with the policy their first change wrote (each judged by the rules).
* bench: change pathstv2026-11-071-1/+2
| | | | | | | Finding the paths changes touch, from documents and from raw change bytes, measured before M6 is built. Auth plan M6 (measure first).
* bench: change signaturestv2026-11-071-1/+2
| | | | | | | Signing and checking change signatures, per change and per actor's latest change, measured before M5 is built (development.md). Auth plan M5 (measure first).
* HyParView flood defaulttv2026-11-061-1/+1
|
* flood disseminationtv2026-11-061-4/+5
|
* HyParView (slim)tv2026-11-061-1/+2
|
* bench repeattv2026-11-061-1/+4
|
* plumtreetv2026-11-061-1/+4
|
* bench several scenariostv2026-11-061-1/+2
|
* bench writes configurabletv2026-11-061-1/+2
|
* tree views measuredtv2026-11-061-2/+2
|
* dashboard: browser checkstv2026-11-051-0/+11
|
* push by defaulttv2026-11-051-2/+1
|
* push changes experimenttv2026-11-051-1/+2
|
* bench tor round tripstv2026-11-051-1/+1
|
* bench mycelium round tripstv2026-11-051-2/+3
|
* benchmark bridge fast linktv2026-11-041-2/+3
|
* benchmark bridge slow linktv2026-11-041-1/+2
|
* benchmark bridgetv2026-11-041-1/+4
|
* benchmark members joiningtv2026-11-041-3/+3
|
* add member away benchmarktv2026-11-031-1/+2
|
* parallel propagation benchmarktv2026-11-031-1/+3
|
* quicker propagation benchmarktv2026-11-031-1/+2
|
* add writer tree benchmarktv2026-11-031-1/+4
|
* add propagation benchmarktv2026-11-031-0/+8
|
* add links relay testtv2026-11-021-0/+5
|
* add documentationtv2026-11-021-0/+52