Skip to content

Add the upstream issue map (tracker × roadmap × backlog) - #43

Merged
eduralph merged 2 commits into
mainfrom
upstream-issue-map
Jul 18, 2026
Merged

Add the upstream issue map (tracker × roadmap × backlog)#43
eduralph merged 2 commits into
mainfrom
upstream-issue-map

Conversation

@eduralph

@eduralph eduralph commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

What & why

Adds docs/upstream-issue-map.md: every open tikv/client-rust issue (72 at the snapshot date) cross-referenced against the roadmap's phases and this repo's backlog issues, with findings — an extended stale-close list (plus two corrections the sweep caught on itself), the filings-should-be-revivals mapping, and the unmapped set. Cross-linked from roadmap §9 and the README layout comment.

Kind of change

  • Gate/harness code (crates/, go/)
  • Scenario / ledger claim (scenarios/, ledger.toml)
  • New or updated finding (findings/)
  • Cluster / tooling (cluster/, Makefile, scripts/)
  • Docs (README.md, docs/)

Checklist

  • make check is green
  • Cluster-backed changes — N/A, docs only
  • No workaround for a client-rust bug
  • README/docs cross-links updated

Evidence

Codex-reviewed at high effort across several rounds; all findings resolved:

The map is snapshot-dated with an explicit re-derive-don't-patch rule.

docs/upstream-issue-map.md maps all 72 open tikv/client-rust issues onto the
roadmap's phases and this repo's backlog (#7-#41). Three findings fell out of
the derivation: five more stale-closable issues than roadmap §9.3 lists (plus
two the sweep itself corrected — #289 is only half-shipped and #239 never
shipped); several planned §9.2 filings should be revivals of existing issues
(#238, #180, #286, #284) rather than new ones; and #531/#327 are candidates
for the Phase-3 long tail. Cross-linked from roadmap §9 and the README layout.

Snapshot-dated and marked re-derive-don't-patch: an issue tracker is not
pinnable, and a stale map is worse than none.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 368b84a5d2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/upstream-issue-map.md Outdated
…cker

Bare #NNN in the map autolinked to this repo instead of tikv/client-rust when
rendered on GitHub, sending readers following the close/revive instructions to
the wrong tracker (and #17 was genuinely ambiguous — both our backlog #17 and
upstream #17). Fully qualify every upstream reference as tikv/client-rust#NNN;
the 'ours' column stays bare, since those correctly resolve here. Pure link
qualification — the July-14 snapshot's content is unchanged.

Signed-off-by: Eduard R. <eduard@ralphovi.net>
@eduralph
eduralph merged commit 3dc9668 into main Jul 18, 2026
5 of 6 checks passed
@eduralph
eduralph deleted the upstream-issue-map branch July 18, 2026 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant