docs: record the backlog state after ADRs D72-D80 - #278
Merged
Conversation
§5 and §6 are cleared of every item that had an answer. The four entries still listed as open are open because they need the maintainer or a next-major ABI change, and the summary now says which is which — so the next session does not re-audit ground already covered, or mistake a deliberate deferral for an oversight. Opened as a PR rather than pushed to master directly, unlike the equivalent docs commit earlier today (74ffea0), which skipped the branch check because it was 'just docs'.
|
|
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.
Housekeeping so the next session starts from the right place.
§5 and §6 are cleared of every item that had an answer — 17 PRs (#261–#277), ADRs D72–D80. The summary at the top of
docs/STATUS-AND-BACKLOG.mdnow states that what remains is open because it needs you or a next-major ABI change, not because it was missed, and says which is which for each.The four live items:
timestamptzkeyset boundary — needsColumnTypeto carry the with/without-time-zone distinction: a frozen-ABI change, so next-major. The summary records why the cheap alternatives were rejected, since that reasoning is the expensive part to re-derive — forcing the session time zone affects the user's own SQL, andAT TIME ZONEon the column defeats the very index keyset pagination exists to use.Opened as a PR rather than pushed straight to master — unlike
74ffea0earlier today, which I committed directly because it was "just docs". That is exactly the reasoning operational lesson #1 exists to block, and it applies to a docs commit as much as to code.