docs(roadmap): Rev 2 — post-v0.7.1 actuals, v0.8 re-slot to One Storage Kernel GA (task #68)#337
Conversation
… to One Storage Kernel GA (task #68) The written roadmap (2026-07-09) predated the v0.7.0 early ship and the storage-kernel build-out that landed inside that train. This revision: - Marks v0.6.1 (folded) and v0.7.0/v0.7.1 shipped, recording the disclosed single-shard-replica limitation and the slipped R5 (keyspace notifications + MONITOR) and R6 (moon:// URI implementation) items. - Re-slots the release train per the 2026-07-15 owner decision: v0.8 = One Storage Kernel GA (close-out + verification of the already-built kernel: task #49 atomic-write stragglers, #56 used_memory truth under offload, spill-file batching, crash-matrix CI, 10×-RAM benchmark report); v0.9 = horizontal scale (cluster-on-monoio + multi-shard replicas); v0.10 = enterprise foundation; v1.0 GA 2027-Q1 unchanged. - Refreshes the reality-check table and debt register: closes the six shipped gaps (multi-shard master PSYNC, WAIT/ACK, cold-tier TTL leak, ACL early-intercept, shardslice waiver, hygiene ledger) and adds the v0.8 close-out items. Refs task #68 (roadmap half; the v0.8 execution plan lives in §4/§8). author: Tin Dang <tindang.ht97@gmail.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
📝 WalkthroughWalkthroughThe documentation updates establish Roadmap Rev 2, set v0.7.1 as the current release, revise capability gaps and replication milestones, update release and execution plans, refresh the debt register, and record the roadmap changes in ChangesRoadmap Rev 2
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 10-12: Update the Roadmap Rev 2 changelog entry to state that
v0.6.1 was folded into v0.7.0 and shipped as part of that train, rather than
describing v0.6.1 as independently shipped. Keep the existing v0.7.0 status and
other roadmap details unchanged.
In `@docs/roadmap/ROADMAP.md`:
- Line 179: Align the v0.9.0 release headline with task C-1’s intended
architecture: update the roadmap entries near the v0.9.0 commitment and C-1 so
they consistently state whether monoio applies to the cluster components or not,
preserving C-1’s explicit control-plane runtime decision unless the planned
architecture is intentionally changed.
- Around line 111-112: Reconcile Section 8.2 with the shipped v0.7 status: mark
the section as historical or replace its R1/R2 implementation plans, replica
tests using s∈{1,4}, and R5/R6 implementation tasks with shipped evidence and
v0.9 follow-up work. Ensure the surrounding roadmap entries consistently show
multi-shard PSYNC and WAIT/ACK as shipped while replica-side multi-sharding and
R5/R6 remain deferred.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9d11747f-3f9b-43f4-92b6-bde1598b7fc8
📒 Files selected for processing (2)
CHANGELOG.mddocs/roadmap/ROADMAP.md
| - **Roadmap Rev 2 (task #68, doc half).** `docs/roadmap/ROADMAP.md` updated to | ||
| post-v0.7.1 actuals: v0.6.1/v0.7.0 marked shipped (with the R5/R6 slips and the | ||
| single-shard-replica disclosure recorded), v0.8 re-slotted to **One Storage |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Clarify v0.6.1’s shipped status.
ROADMAP.md says v0.6.1 was folded into v0.7.0 and shipped inside that train; it is not independently marked as shipped. Please align this changelog wording with the roadmap.
Proposed wording
- post-v0.7.1 actuals: v0.6.1/v0.7.0 marked shipped (with the R5/R6 slips and the
+ post-v0.7.1 actuals: v0.6.1 folded into the shipped v0.7.0 train (with the R5/R6 slips and the📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - **Roadmap Rev 2 (task #68, doc half).** `docs/roadmap/ROADMAP.md` updated to | |
| post-v0.7.1 actuals: v0.6.1/v0.7.0 marked shipped (with the R5/R6 slips and the | |
| single-shard-replica disclosure recorded), v0.8 re-slotted to **One Storage | |
| - **Roadmap Rev 2 (task `#68`, doc half).** `docs/roadmap/ROADMAP.md` updated to | |
| post-v0.7.1 actuals: v0.6.1 folded into the shipped v0.7.0 train (with the R5/R6 slips and the | |
| single-shard-replica disclosure recorded), v0.8 re-slotted to **One Storage |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 10 - 12, Update the Roadmap Rev 2 changelog entry
to state that v0.6.1 was folded into v0.7.0 and shipped as part of that train,
rather than describing v0.6.1 as independently shipped. Keep the existing v0.7.0
status and other roadmap details unchanged.
| Multi-shard master PSYNC GA v0.7 | ||
| Real WAIT + ACK v0.7 |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Reconcile the shipped v0.7 status with the remaining v0.7 workstreams.
The mindmap and heading say multi-shard PSYNC and WAIT/ACK shipped, with replica-side multi-sharding and R5/R6 deferred. However, Section 8.2 still presents R1/R2 as implementation workstreams, tests replicas with s∈{1,4} on Line 337, and describes R5/R6 implementation tasks on Lines 354–369. Mark this section as historical or replace it with shipped evidence and v0.9 follow-up tasks; otherwise the roadmap contradicts its own release status.
Also applies to: 324-324
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/roadmap/ROADMAP.md` around lines 111 - 112, Reconcile Section 8.2 with
the shipped v0.7 status: mark the section as historical or replace its R1/R2
implementation plans, replica tests using s∈{1,4}, and R5/R6 implementation
tasks with shipped evidence and v0.9 follow-up work. Ensure the surrounding
roadmap entries consistently show multi-shard PSYNC and WAIT/ACK as shipped
while replica-side multi-sharding and R5/R6 remain deferred.
| | **v0.7.0** | ✅ **shipped 2026-07-14** | **Replication GA for multi-shard masters** | The HA unblock; also absorbed storage-kernel M0–M4 | | ||
| | **v0.7.1** | ✅ **shipped 2026-07-15** | SQ8 CPU-storm fix + deterministic replica TTL | Patch | | ||
| | **v0.8.0** | 2026-08 | **One Storage Kernel: kill-9-lossless on every plane + 10× RAM datasets** | Close-out + verification of the already-built kernel (owner decision 2026-07-15) | | ||
| | **v0.9.0** | 2026-10 | **Horizontal scale: cluster GA-hardened on monoio + multi-shard replicas** | Re-slotted from v0.8; adds the replica-side shard gap | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Align the v0.9 monoio commitment with task C-1.
The release headline promises cluster GA hardening “on monoio,” but C-1 on Line 375 explicitly keeps the control plane on a dedicated thread with a current-thread tokio runtime and says not to port it to monoio. Choose and document one intended architecture so the release commitment and execution plan do not drive opposite implementations.
Also applies to: 371-371
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/roadmap/ROADMAP.md` at line 179, Align the v0.9.0 release headline with
task C-1’s intended architecture: update the roadmap entries near the v0.9.0
commitment and C-1 so they consistently state whether monoio applies to the
cluster components or not, preserving C-1’s explicit control-plane runtime
decision unless the planned architecture is intentionally changed.
2 participants
Summary
Roadmap Rev 2 (task #68, doc half): reconcile
docs/roadmap/ROADMAP.mdto post-v0.7.1 reality and record the 2026-07-15 owner decision on the release train.What changed
moon://URI implementation) recorded for v0.9 re-ranking.used_memorytruth under offload, spill-file batching, crash-matrix scheduled CI, G2 real-disk re-run + published 10×-RAM benchmark report.Verification
Doc-only change. CHANGELOG
[Unreleased]entry included (Lint gate).Summary by CodeRabbit