Mirror
/
seaweedfs
mirror of https://github.com/seaweedfs/seaweedfs.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13127 Commits
130 Branches
331 Tags
368 MiB
 
 
 
 
 
 
Tree: bdf20fde71
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'bdf20fde71'
${ noResults }
seaweedfs/sw-block
pingqiu bdf20fde71
feat: Phase 12 — production hardening (disturbance, soak, testrunner scenarios) 		19 hours ago
..
.gocache_v2 feat: add V2 protocol simulator and enginev2 sender/session prototype 6 days ago
.private feat: Phase 12 — production hardening (disturbance, soak, testrunner scenarios) 19 hours ago
bridge/blockvol fix: update contract.go field source docs to match P1 implementation 4 days ago
design feat: Phase 09 — V2 execution primitives and production closure 19 hours ago
engine/replication feat: Phase 09 — V2 execution primitives and production closure 19 hours ago
private feat: add V2 protocol simulator and enginev2 sender/session prototype 6 days ago
prototype fix: stable ServerID in assignments, fail-closed on missing identity, wire into ProcessAssignments 3 days ago
test feat: add V2 protocol simulator and enginev2 sender/session prototype 6 days ago
README.md feat: add V2 protocol simulator and enginev2 sender/session prototype 6 days ago

README.md

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-block product structure clean enough to split into a separate repo later if needed

Suggested layout:

  • design/: shared V2 design docs
  • prototype/: 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 inside seaweedfs
  • likely future state: sw-block becomes a standalone sibling repo/product
  • design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths