mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-14 01:58:33 +02:00
pingqiu
ba7bd0ba48
Architect approves v0.4.4 substance (Option B; master unchanged; no PeerSetGeneration change) but requires five doc-hygiene fixes before single-sign: 1. §1 #3 V2 path "weed/server/" → V3 "core/replication/" + reword from "shipper re-arms" V2 vocabulary to "probe loop detects degraded peer reconnection". 2. §1 Architecture truth-domain check: dropped v0.3 / A1 / "publication / re-emission" residue. Now points cleanly to §1.C. 3. §2 "#3a/#3b/#4" v0.2 naming residue: rewritten to reference acceptance criteria #2-#15 with package-level verifier files (peer_test.go, probe_loop_test.go, volume_test.go, component/). Test method names concretized at code-start as commit-note addendum (no re-ratification needed). 4. Architect review checklist "Engine / adapter impact" reworded: "No new engine recovery primitive by default; engine-owned fences/state audited at §1.H code-start; if found insufficient, sw halts G5-5C and starts engine-evolution mini-plan rather than layering ifs in core/replication/." 5. §1.A loop owner row bound: probe loop placement = core/replication/ owned by ReplicationVolume lifecycle (NOT host layer). Reasoning: admitted peers + peer state + close/teardown + in-flight guard all in core/replication/; host only forwards flags/config. §1.H halt rule preserved: audit may still escalate to engine-evolution. §7 sign table records substance approval 2026-04-27 + probe loop placement binding + awaits single-sign of v0.4.5. Standing by for architect single-sign.
sw-block
Private WAL V2 and standalone block-service workspace.
Purpose:
- keep WAL V2 design/prototype work isolated from WAL V1 production code in
weed/storage/blockvol - allow private design notes and experiments to evolve without polluting V1 delivery paths
- keep the future standalone
sw-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: code prototypes and experiments.private/: private notes, phase development, roadmap, and non-public working material
Repository direction:
- current state:
sw-block/is an isolated workspace insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths