Add the upstream issue map (tracker × roadmap × backlog) - #43
Merged
Conversation
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>
There was a problem hiding this comment.
💡 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".
…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>
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.
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
crates/,go/)scenarios/,ledger.toml)findings/)cluster/,Makefile,scripts/)README.md,docs/)Checklist
make checkis greenEvidence
Codex-reviewed at high effort across several rounds; all findings resolved:
#NNNrefs autolinked to this repo, misdirecting readers who follow the close/revive instructions (and#17was ambiguous — both our backlog 5.1 Typed error taxonomy (starts with #[non_exhaustive] on Error) #17 and upstream 5.1 Typed error taxonomy (starts with #[non_exhaustive] on Error) #17); every upstream reference is now fully qualifiedtikv/client-rust#NNN, theourscolumn stays bare;The map is snapshot-dated with an explicit re-derive-don't-patch rule.