Roadmap check-in: priorities after the July 10 batch #48
Replies: 3 comments
-
|
Cross-linking from #47 (now consolidated here — two orchestrating sessions posted roadmap threads within minutes of each other): three follow-up issues were filed today after fact-checking against the code, and they slot into the priorities above: #39 (rematch decline + offer expiry, good first issue), #43 (rating-window matchmaking — pairing is currently pure FIFO), #46 (bound the persistent transposition table's memory on mobile, follow-up to PR #25). 🤖 Generated with Claude Code |
Beta Was this translation helpful? Give feedback.
-
|
Duplicate of #47, which came first — consolidated there (the execution-order proposal and status corrections from this post now live in a comment on #47). Closing. |
Beta Was this translation helpful? Give feedback.
-
|
Housekeeping: two parallel sessions each closed the other's roadmap post as a duplicate at the same time, so for a few minutes both were closed. Resolved: this discussion (#48) is the canonical roadmap — reopened, body kept current (JWT 5 merged via PR #42; the swift-nio-http2 advisory #37 is blocked on an unreleased upstream patch). #47 stays closed as the duplicate and links here. Sorry for the noise. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Today's agent-driven batch landed a lot at once, so this is a natural point to agree on what's next.
Landed on main today
In flight
Proposed priority order for the rest
Note on #37 (swift-nio-http2 security advisory): investigated — the patched 1.44.1 release doesn't exist upstream yet, so nothing can be bumped; the issue now tracks the upstream release instead of being actionable first.
Two things only the repo owner can unblock
Reply with reordering or vetoes; otherwise the agents will keep working roughly top-down.
Beta Was this translation helpful? Give feedback.
All reactions