aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/README.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 04:00:12 +0000
committertv <tv@krebsco.de>2026-11-19 05:13:38 +0100
commit0d2467e15ec0c9c035b1074a2dd4eece6b24c599 (patch)
treee544ce8ae1c31e9556191d3f99157b5bd61b1f14 /docs/guides/federation/README.md
parentefaf79e7fd55db2b9704ccefedde33346f874a1d (diff)
federation: revisions shown, named, and moved to by hand
An operator moving the federation to a revision had nothing to say which revisions a node knows, nor which one the current version follows, and a hash where a name would do. `GET /events` lists the revisions the node's continuum knows, each its number, its ID, the feature it adds and what that adds, and as people read it ("revision 1 (merge-events)"); `GET /events/counts`, the current version's. `continuum-party next --revision FEATURE` begins a version following the revision adding it, never an earlier one than the current version's, and `next` says so where the node knows a later one. `proposals` shows a change of revision as people read it, a revision this continuum doesn't know so said. A client backs a version moving to a revision only where its node knows it, and says why otherwise: once passed, a node that doesn't stops there. The upgrades guide walks through moving to a revision: upgrade every node, propose, vote, and what follows; the proposing guide lists `revision`, and the API's spec the rest.
Diffstat (limited to 'docs/guides/federation/README.md')
-rw-r--r--docs/guides/federation/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/guides/federation/README.md b/docs/guides/federation/README.md
index 32f8756..4c5b33b 100644
--- a/docs/guides/federation/README.md
+++ b/docs/guides/federation/README.md
@@ -30,8 +30,8 @@ by them, in its words.
is its own, the store file, dropping events and taking them back.
* [`remakes.md`](remakes.md): compactions only, the electorate, the snapshot, putting
again after a switch, two epochs for one, and rejoining.
-* [`upgrades.md`](upgrades.md): upgrading the nodes of a federated swarm, and what the
- federation's number and its revision say.
+* [`upgrades.md`](upgrades.md): upgrading the nodes of a federated swarm, what the
+ federation's number and its revision say, and moving to a later revision.
* [`watching.md`](watching.md): what a node's API and its log say that needs an operator
or a party.
* [`building-on-the-api.md`](building-on-the-api.md): an application reading what