mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 13:30:46 +02:00
pingqiuandClaude Opus 4.6
275c3ee1c7
Tighten acceptance matrix with explicit per-boundary rows, signoff reading split into hard blockers vs product hardening, and clear rule: architecture-complete ≠ product-complete. 6 hard blockers before T6/T7: 1. WriteLBA/SyncCache/sync_all contract closure 2. Fresh replica bounded catch-up before live tail 3. Timeout/retention-loss classification for catch-up 4. publish_healthy alignment with one protocol contract 5. RF=2 stable identity on all shipping paths 6. Test audit for incorrect WriteLBA==commit assumptions Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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