Repository navigation
The Phase 3 backlog lists the specialist picks, US-58 to US-64 - #398
Open
ARSH871-bot wants to merge 1 commit into
Open
ARSH871-bot wants to merge 1 commit into
ARSH871-bot wants to merge 1 commit into
Conversation
The seven picks agreed on 13 October were filed as issues #391 to #397 straight from the team's slate, so the backlog document -- generated from tools/make_phase3_backlog.py -- no longer listed every story in the milestone. They join EXISTING, the list the script folds in rather than creates, so no run of the script can open them a second time. US-53 (#220) moves to Shubham, who took it on as a specialist pick the same day. The distribution line follows from the lists rather than being typed: 45 stories, Arsh 29, Ankeet 7, Shubham 4, Samika 5. The document is regenerated with `python -m tools.make_phase3_backlog doc`, not edited, so tests/test_phase3_backlog_doc.py still holds.
shubhamkataria2005
approved these changes
Oct 13, 2026
shubhamkataria2005
left a comment
Collaborator
There was a problem hiding this comment.
Approving. Verified by regeneration, not by reading the diff:
- Merged onto current
main, ranpython -m tools.make_phase3_backlog doc(no GitHub calls), and the output is byte-identical to the committed document.tests/test_phase3_backlog_doc.py: 5 passed. - The ownership it records matches GitHub. #220 is assigned to me, and #391–#397 are assigned exactly as the specialist table says: Arsh #391–392, Ankeet #393–395, Samika #396–397.
- The distribution line is computed, not typed, which is the right call for the one sentence people quote.
Taking #220 (US-53) — I will comment there once I have sized it, ahead of planning on 19 October.
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.
The Phase 3 backlog document now lists the seven specialist picks agreed on 13 October (US-58 to US-64, #391 to #397), and records #220 as Shubham's. Until this merges,
docs/design/phase-3-backlog.mdmisstates the milestone: seven of its stories are missing and one has the wrong owner.What changed
All of it goes through the generator. The document is regenerated, not edited, because
tests/test_phase3_backlog_doc.pyrequires it to matchtools/make_phase3_backlog.pybyte for byte.tools/make_phase3_backlog.pyEXISTING, the list the script folds in rather than creates.createskips them, so no run can open them a second time. US-53's owner becomes Shubham. ASpecialistepic, a row in "Where these came from", and a line in the order-of-work block, which the script checks against the stories.docs/design/phase-3-backlog.issues.jsonUS-58toUS-64mapped to#391to#397docs/design/phase-3-backlog.mdpython -m tools.make_phase3_backlog doc, which makes no GitHub callsThe distribution line is computed from the lists, not typed:
Sizes show as
TBC. The issues leave sizing to each owner at sprint planning on 19 October, and the document should not guess one.Evidence
The guards were checked against a mutation, not just run green. With
US-64removed from the numbers file and one line of the document hand-edited:Both restored: 5 passed. The committed document has 0 CR bytes and is byte-identical to
document(), so the check holds on CI's Linux runners as well as on Windows.On #249
This is my second open PR beside #386, which #249 says I should not do. It is opened under that rule's exception for fixing something already wrong: the document misstates the milestone until it merges. #387 to #390 are next in my queue.
Reviewer: @shubhamkataria2005, because the one change here that is not mechanical is US-53 (#220) being recorded as yours.