docs: clustering release train — per-release R5 breakout - #423
Merged
Merged
Conversation
… 2026-08-13)
R5 was too coarse ("0.4→1.0") to create prioritization pressure. Break the
clustering work into a release train so each cut notches a concrete clustering
win (release-dimensions rule):
0.5 cluster shows truth + reconfigures (membership, quorum reconfig, peer-crash, auth)
0.6 distributed lock manager (DLM/ENQ, RMS arbitrator)
0.7 real-VAX interop hardening (the RE friction bugs)
0.8 rejoin 5/5 white-whale + diskless satellite boot
1.0 join a real cluster + evacuate (the takeover bar)
Items carry rel-<milestone> labels so `rd list` shows what a cut owes. Records
the vms-2f3 thesis: forward features (quorum reconfiguration) are the likeliest
way to surface the residual 1/5 rejoin root cause.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
baron-3dl
added a commit
that referenced
this pull request
Aug 13, 2026
#445) Bump OVMX_PRODUCT_VERSION V0.4 → V0.4-1. 24 PRs / 32 commits since V0.4, packed across dimensions (point release toward the 0.5 milestone): self-host (R7) #409 lib$tparse · #411 CLI$ compiled-CLD · #413 sys$setddir #414 lib$get_foreign · #415 sys$filescan (RTL foundation) #418 parse_tables.mar→C (spine #2) · #429 LIBRARIAN.EXE+.OLB (spine #3) #435 shareable-vector freeze (GSMATCH stability) authenticity #421 veracity rubric (Q1 oracle-source/Q2 real-inject) · #424 30 oracle-pinned constants #433 rmsdef.h 74 fabricated RMS codes → oracle UX/DCL/RMS #422 SHOW CLUSTER real membership · #441 DCL per-@-level local scope #442 RMS XAB dates → VMS 1858-epoch quadword networking #419 virtio NIC (user-mode default + opt-in tap/bridge) docs #423 clustering release train + swept: other threads' merged work on main since V0.4 Clustering config-authoring UX (vms-098) + its public-manual grounding gate remain 0.5 (minor) deliverables — not triggered by this point cut. Co-authored-by: alice <alice@workspace.local> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Operator asked (2026-08-13) to map each clustering track to a target release so there's release pressure prioritizing them.
Breaks the coarse R5 gate ("0.4→1.0") into a per-release clustering train in
docs/release-roadmap-to-1.0.md, and appliesrel-<milestone>labels to every item sord listsurfaces what each cut owes:🤖 Generated with Claude Code