docs: v10 roadmap from v9 deep-dive review#5
Merged
Conversation
This was referenced Jul 2, 2026
Closed
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
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.
Deep-dive code review of v9.0.0 (3,069 LOC, 11 modules) and a phased plan to v10.
TL;DR: v9 is healthy — the v8→v9 rewrite closed most classic footguns (filter_mode, main-thread pause cache, typed config fallbacks, bounded mpv terminate, gen counter, token-gated shutdown). So v10 is a next-level release, not a bug-fix.
Six epics
hyperwall_v8.exe/9.0string drift (~15 refs) and decouple G-Sync isolation from the literal basename before bumping the version. Foundation._switchingerror-path leak fix, memory-aware cache budget, crash-loop guard._build_url/needs_transcode/retry transitions/config round-trip + GitHub Actions.MediaBackendprotocol → Emby + Jellyfin.Sequencing: v10.0 = epics 1+2+3 · v10.1 = 4 · v10.2 = 5 · v10.3 = 6.
Guardrails carried forward:
static=trueis load-bearing (Emby 4.9.5.0 500 bug), validate against a live server, no speculative behavior, build hygiene.Full detail with file:line references in
ROADMAP.md. This PR adds the roadmap doc only — no code changes.📍 Tracked as GitHub issues (milestone v10)
Sequencing: v10.0 = #6 + #7 + #8 · v10.1 = #9 · v10.2 = #10 · v10.3 = #11
Milestone: https://github.com/tcconnally/hyperwall/milestone/1