mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-03 06:37:09 +00:00
pingqiu
a15d13a02c
Per v3-batch-process.md §2: §close drafted as soon as software is ready. Hardware row table left as TBD; sw fills evidence pointers once iterate-m01-replicated-write.sh completes. Forward-carries + deferred ledger pointers + architect-review-checklist all populated based on G5-5C scope already in-batch. Awaiting: 1. m01 hardware run completion → fill #1-#4 evidence rows 2. QA evidence verification → §close.deltas / findings if needed 3. architect single-sign per v3-batch-process.md §5 + §8C.2
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