From b710146b9e17d844a1e2647a2b43eeadd62893aa Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 18:55:17 +0000 Subject: continuum-party: forks by what they are for, by a proposal, at the node's heads `fork` took a version written by hand and every head by name. Now: * fork FILE [HEAD...]: the heads the node shows where none are named; * fork proposal PROPOSAL: by the version of a proposal on the current version, as a fork's version is usually one that didn't pass; * fork admit, remove, give, take, keys, nodes, revision: by the next version changed as they say, as propose does (not checkpoint: a fork is at heads of its own); each subcommand taking --at HEAD... and --founder PARTY=NODE,..., which names a party's node list anew in the fork's version, so that the nodes its founders run it on are members there. --- CHANGELOG.md | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index b2664b6..7840755 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,12 @@ it from the release before ([`docs/operations.md`](docs/operations.md), ## Unreleased +* `continuum-party fork` takes the changes `propose` does, or a proposal's version + (`fork proposal PROPOSAL`), forking at the heads the node shows unless others are named + (`--at`); `--founder PARTY=NODE,…` names a founder's node list anew in the fork + ([`docs/guides/federation/forking-and-following.md`](docs/guides/federation/forking-and-following.md); + [`src/federation/party.rs`](src/federation/party.rs)). + * `continuum-party propose` takes the changes made most by what they are for: `admit`, `remove`, `give`, `take`, `keys`, `nodes`, `checkpoint` and `revision` write the next version so and propose it. Every proposal says first what it does, and asks on a -- cgit v1.3.1