docs(pivot): sweep tracking docs for wave-3/4 landings#212
Merged
Conversation
Reconcile RFC-0013 + CHANGELOG + MILESTONES + migration guide with the wave-3 (PR-B1-shape sibling ports) and wave-4 (PR-B2-shape upstream-only ports + PR-F.1 + PR-J + PR-L + PR-N) landings: - docs/rfcs/0013-distro-first-pivot.md §migration: mark PR-A2 (#189), PR-B2 (#201), PR-F.1, PR-G (#182), PR-H (#183), PR-L (#179 skeleton + #191 body), PR-N (#200) landed. Re-scope PR-F.2 to delete the whole internal/{component status,pipeline,pipelinebuilder,consumer,fanout,runtime/lifecycle} bundle in one cut once the three open ports (#204 / #205 / #207) land. Note PR-I.1a in flight, PR-I.1b gate satisfied by #201, PR-K.1 in flight. Record the wave-3-followup sibling ports (#202/#203/#208/#209) under PR-B2 to dispel the slug collision with #188's PR-B2-labelled dcgm port. - CHANGELOG.md [Unreleased]: restructure the pivot wave list as four waves (was three) — wave 3 enumerates PR-B1-shape sibling ports + support infra (#180-#194/#196), wave 4 enumerates PR-B2-shape upstream-only ports + PR-J (#195) + PR-F.1 (#206) + PR-N (#200) + lint/TOCTOU hardening (#198/#210). Tighten the PR-F.2 deferred note to point at the three open ports as the gate. - MILESTONES.md: M1 + M2 + M8 status rows now cite PR-A2/#189, PR-F.1/#206, PR-E/#180, PR-J/#195. M8 dcgm flipped to landed-and-replaced. - docs/migration/v0.1-to-v0.2.md: §PR-F status flips from "not yet open" to "PR-F.1 landed, PR-F.2 gated on three open ports". Open-items checklist expanded to track every PR letter (A2 / E / F.1 / F.2 / I.1a-c / J / K.1-3 / L / N) with PR numbers and links. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Signed-off-by: Tri Lam <tri@maydow.com>
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.
Summary
Reconcile the four pivot-tracking docs (
docs/rfcs/0013-distro-first-pivot.md,CHANGELOG.md,MILESTONES.md,docs/migration/v0.1-to-v0.2.md) with the wave-3 (PR-B1-shape sibling ports) and wave-4 (PR-B2-shape upstream-only ports + PR-F.1 + PR-J + PR-L + PR-N) landings. Pure doc sweep — no code or config touched.What changed
docs/rfcs/0013-distro-first-pivot.md§migrationPR sequence rows updated with PR-number citations and landed markers:
internal/{selftelemetry,telemetry}+components/receivers/dcgm/+pkg/dcgm/+ one orphan clockreceiver integration test)internal/{componentstatus,pipeline,pipelinebuilder,consumer,fanout,runtime/lifecycle}bundle in one cut once the last three pipeline+consumer-importing receivers land (feat(pivot): port k8sevents off internal pipeline+consumer to upstream #204 k8sevents, feat(pivot): PR-B3 — port clockreceiver off internal pipeline+consumer #205 clockreceiver, feat(pivot): port otlphttp off internal pipeline+consumer to upstream #207 otlphttp). Per the import-graph state —internal/componentstatus's only non-test consumer isinternal/pipeline, so they delete togetherdocs/migration/v0.2-to-v0.3.mdCHANGELOG.md[Unreleased]MILESTONES.mdinternal/config/(still load-bearing fortracecore validate).internal/componentstatusas travelling withinternal/pipelinein PR-F.2.docs/integrations/prometheus-scrape.mdrecipe. Notes the inert chart toggle retention until PR-K.3.docs/migration/v0.1-to-v0.2.mdinternal/*package deletion (PR-F) status flips from "not yet open" to "PR-F.1 landed (feat(pivot): PR-F.1 — delete internal moats (selftel/telemetry) + dcgm #206), PR-F.2 gated on three open ports".Why now
Tracking docs accumulated drift across wave-3 + wave-4 because every sibling-port PR (and the support-infra PRs around them) updated the bottom of
CHANGELOG.mdbut did not always touch the upstream sequencing section in RFC-0013. Per memory rule[Keeping this document current]: status drift is a review blocker. This PR is the consolidated catch-up; future port PRs include their RFC-row flip in-PR.What this PR does NOT change
Test plan
bash scripts/doc-check.shclean (33 test refs, 528 links resolve, comment-noise diff gate clean vsorigin/main, all 13 gates green).commitlint72-char subject limit + DCO + AI-trailer gates) passed.make ci-fastequivalent:golangci-lint,go vet,go mod verify,no-autoupdate-check,doc-check.sh) passed on second attempt aftergit fetch origin mainpopulated the worktree'sorigin/mainref — first push failed because the worktree previously tracked the (gone)pr-a2-ocb-main-swapbranch, sodoc-check.sh's comment-noise diff-scope gate exited 128 on the missing ref. Root cause fixed by the fetch; not a workaround.