diff options
Diffstat (limited to 'docs/guides/federation')
| -rw-r--r-- | docs/guides/federation/upgrades.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index 6ffde67..9025164 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -10,10 +10,11 @@ design's ([`federation.md`](../../federation.md), A node of a federated swarm upgrades as any node does ([`operations.md`](../../operations.md), [Upgrading](../../operations.md#upgrading)), restarted with its files, and a release's version says how: a patch or a minor release one -node at a time, a major one every node close together. Across a change of the wire -format, a major one, upgraded nodes and the others don't talk, and the swarm is split -until all are upgraded; a remake needs the same Automerge on every node, and one with -another rejoins instead of switching. Before 1.0.0, take every upgrade as a major one. +node at a time, a major one every node close together. Nodes write each other the newest +wire version both speak; where two releases share none, a major one, upgraded nodes and +the others don't talk, and the swarm is split until all are upgraded. A remake needs the +same Automerge on every node, and one with another rejoins instead of switching. Before +1.0.0, a release's tag says whether it is a flag day. Nobody runs every node of a federated swarm: each party's operators upgrade its nodes. A patch or minor release each party takes when it likes; for a major one, agree on when, |
