File items 469 and 470: move do-epic's parent issues and start issues by score #661
@@ -6,16 +6,18 @@
|
||||
|
||||
`Bar = 0.1`
|
||||
|
||||
`Next ID = 469`
|
||||
`Next ID = 471`
|
||||
|
||||
## Items
|
||||
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 469 | 0.15.0 | | | **Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.** | 3 | 2 | 2 | 5 | 4 | 1.2 by 4, 1.5 by 4, 1.6 by 3 | 3.1 |
|
||||
| 453 | 0.15.0 | | | **Make the issue types that do-epic and `todo-item add` file in Jira settings, since a Jira project such as TW has no Task type.** | 2 | 2 | 1 | 3 | 2 | 1.6 by 5 | 1.8 |
|
||||
| 454 | 0.15.0 | | | **Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4 | 1.1 |
|
||||
| 467 | 0.15.0 | 453, 454 | question | **Cut 0.15.0 as soon as items 449, 450, 453 and 454 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
|
||||
| 470 | 0.15.0 | | | **Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.** | 3 | 2 | 2 | 5 | 5 | 1.2 by 4, 1.6 by 3 | 1.5 |
|
||||
| 468 | 0.15.0 | | | **Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.** | 2 | 2 | 2 | 4 | 2 | 1.6 by 4 | 1.4 |
|
||||
| 454 | 0.15.0 | | | **Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4 | 1.1 |
|
||||
| 467 | 0.15.0 | 453, 454, 468, 469, 470 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
|
||||
| 446 | 0.16.0 | | question | **Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 3 | 1.0 |
|
||||
| 462 | 0.16.0 | | | **Run under `mutate-changes` the tests that today fail in mutmut's copy of the tree, so a mutant of a line only they cover is killed.** | 2 | 1 | 2 | 3 | 3 | code health by 3 | 4.7 |
|
||||
| 77 | 0.16.0 | | | **Teach `bin/metric-bench` Go and TypeScript, rerun it once two projects' comprehension histories name places, and bring into review only a metric that tracks the panel.** | 4 | 2 | 1 | 5 | 6 | 1.1 by 7, 1.4 by 7 | 2.1 |
|
||||
@@ -75,6 +77,35 @@
|
||||
|
||||
## Details
|
||||
|
||||
### 469. Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.
|
||||
|
||||
do-epic moves to done only a parent it split itself (`split_items_closed`). A parent whose sub-tasks a person filed stays as Jira holds it, and `--status` says "its sub-tasks are done; close it in Jira". Until someone moves it, the parent blocks every issue it blocks, and through it their sub-tasks. On TW-13503, TW-13505 blocks most of the critical path this way, and TW-13547's sub-tasks are all Release Ready while the parent stays In Progress. The human asked, on 2026-11-20, for deterministic code to move these parents, not a worker or a person.
|
||||
|
||||
- A parent whose sub-tasks have all landed, each in one of `jira-unblocking-statuses` or done, with at least one not yet done, moves by a transition the config names, such as `jira-landed-transition = "Release Ready"`.
|
||||
- A parent whose sub-tasks are all done moves by `jira-finish-transition`, as a split item does today.
|
||||
- do-epic moves such parents as each run plans, and after each chunk finishes, where it now closes split items. A parent already at or past the target status stays: one in a done status never moves back.
|
||||
- A parent with no sub-tasks, or with one sub-task still open, is left alone.
|
||||
- Without `jira-landed-transition`, only the move to Done happens, and only where `jira-finish-transition` is set, as today.
|
||||
- `--dry-run` prints each parent move it would make.
|
||||
|
||||
Choice, made 2026-11-20: a sub-task in any of `jira-unblocking-statuses` counts as landed, so TW's "Teach & Learn" counts as "Release Ready" does. The human named Release Ready and Done; Teach & Learn also means the work merged.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/main.py`: `split_items_closed`, `planned_and_started` (small)
|
||||
- `bin/do_epic/planning.py`: `planned` (small)
|
||||
- `bin/do_epic/scheduler.py`: `chunks` (small)
|
||||
- `bin/do_epic/split.py`: `finished` (small)
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load` (small)
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicStore`
|
||||
- `bin/do_epic/backend/jira.py`: `JiraEpic`
|
||||
- `bin/do_epic/backend/fake.py`: `MemoryEpic`
|
||||
- `bin/do_epic/backend/contract.py`
|
||||
- `bin/do_epic/dry_run.py`
|
||||
- `bin/do_epic/test_do_epic.py`
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 453. Make the issue types that do-epic and `todo-item add` file in Jira settings, since a Jira project such as TW has no Task type.
|
||||
|
||||
do-epic and `todo-item add` file every new issue as a Task, the name `plan_store/jira_epic.py` sets as `ISSUE_TYPE`. A Jira project without a Task type, such as TW, whose types are Feature, Bug, Chore and Investigation, refuses each one. So `do-epic --file` fails there, and so does the epic's finishing, which files a release review for each repo.
|
||||
@@ -93,6 +124,44 @@ Touches:
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 470. Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.
|
||||
|
||||
do-epic starts the issues it may run in Jira's backlog order (`scheduler.chunks`). It scores and ranks only the issues it filed itself (`planning.ranked_keys`); a person's issue holds no scores and keeps the rank the team gave it. The human asked, on 2026-11-20, that only the score decide priority on an epic such as TW-13503, where people filed every issue.
|
||||
|
||||
- As it plans, do-epic scores each open issue that may become a chunk and holds no scores: L, E, I, S and Moves against the chain of goals `ranking.py` uses (the epic's, then code health, then the repo's). It writes the scores to the issue's `plan-item` property, as `todo-item edit` does on a person's issue, with a comment, in the epic's language, telling the team the issue is scored and why.
|
||||
- Scores a person wrote, or that an earlier run wrote, stay as they are.
|
||||
- `scheduler.chunks` orders the runnable issues by score, highest first, with each blocker lifted above what it blocks, as `rank_todo.py` does. An issue that couldn't be scored comes last, in backlog order, and `--status` says why.
|
||||
- A sub-task is scored on its own, against its own repo's goals.
|
||||
- The board's rank of a person's issue stays as the team set it. Choice, made 2026-11-20: start order is do-epic's decision, the board order is the team's (goal 1.6). do-epic still re-ranks the issues it filed.
|
||||
- `--dry-run` prints the scores it would write and the order it would start in.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/planning.py`: `planned`, `ranked_keys`, `item_of`
|
||||
- `bin/do_epic/ranking.py`: `ranked` (small)
|
||||
- `bin/do_epic/scheduler.py`: `chunks`, `start_chunks`
|
||||
- `bin/do_epic/main.py`: `planned_and_started` (small), `status_printed` (small)
|
||||
- `bin/do_epic/backend/protocol.py`: `EpicStore`
|
||||
- `bin/do_epic/backend/jira.py`: `JiraEpic`
|
||||
- `bin/do_epic/backend/fake.py`: `MemoryEpic`
|
||||
- `bin/do_epic/backend/contract.py`
|
||||
- `bin/do_epic/dry_run.py`
|
||||
- `bin/do_epic/test_planning.py`
|
||||
- `bin/do_epic/test_do_epic.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 468. Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.
|
||||
|
||||
Item 449 makes do-epic record a repo pick, and each sub-task it files, under the team's own label from the `[label-repos]` table (`repo_pick.label_of(pick, team)`). The instructions do-epic gives a chunk's worker still name only `repo:<name>`: `LABELS` in `bin/do_epic/findings.py` (used in `HELP` at findings.py:31, in `instructions` at :48, and in `written`'s refusal at :99 and its reply at :105) and the `--file ... --label repo:<name> --label do-epic-release-review` command in `finish.task` at `bin/do_epic/finish.py:60`. A team whose board uses its own labels therefore still gets a finding or a release review labelled `repo:core-4` where it expects `core-4`.
|
||||
|
||||
Give both prompts the team's label for each repo of the table where the table names it (`repo_pick.team_label`, `also`), and keep `repo:<name>` for a repo the table doesn't name. `finish.task` already knows each repo that lacks its review, so it can name each one's label outright, as `label_of(Repo(name), team)` gives it. The README states the pick's spelling (`repo-rule.md`'s bullet) but not the finding's, so it needs no change.
|
||||
|
||||
Touches:
|
||||
- `bin/do_epic/findings.py`: `LABELS`, `instructions` (small), `written` (small)
|
||||
- `bin/do_epic/finish.py`: `task` (small)
|
||||
- `bin/do_epic/test_findings.py`: `Instructions`
|
||||
- `bin/do_epic/test_finish.py`: `TheFinishingChunksTask`
|
||||
|
||||
### 454. Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.
|
||||
|
||||
When a do-epic chunk starts, its issue stays as Jira holds it: unassigned, in New and outside the sprint. A team whose board shows who works on what, such as TW, where an issue being worked is assigned to the person, In Progress and in the active sprint, then sees nothing of the loop's work. Today each worker would have to do this by hand, from rules only some machines hold.
|
||||
@@ -112,7 +181,7 @@ Touches:
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 467. Cut 0.15.0 as soon as items 449, 450, 453 and 454 have merged, before its release review, and run that review in 0.15.1.
|
||||
### 467. Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.
|
||||
|
||||
lilleman's call on 2026-11-20: they need what 0.15.0 holds to work, so 0.15.0 is cut without a release review. This item holds the loop back from starting 0.15.0's release review once its last item merges: it waits as a question, so the human, or the session that cuts, drops it at the cut. At the cut, an item in 0.15.1 runs the release review, and the review's follow-ups land in 0.15.1.
|
||||
|
||||
@@ -120,18 +189,6 @@ Touches:
|
||||
|
||||
- `CHANGELOG.md`: `## Unreleased` (small)
|
||||
|
||||
### 468. Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.
|
||||
|
||||
Item 449 makes do-epic record a repo pick, and each sub-task it files, under the team's own label from the `[label-repos]` table (`repo_pick.label_of(pick, team)`). The instructions do-epic gives a chunk's worker still name only `repo:<name>`: `LABELS` in `bin/do_epic/findings.py` (used in `HELP` at findings.py:31, in `instructions` at :48, and in `written`'s refusal at :99 and its reply at :105) and the `--file ... --label repo:<name> --label do-epic-release-review` command in `finish.task` at `bin/do_epic/finish.py:60`. A team whose board uses its own labels therefore still gets a finding or a release review labelled `repo:core-4` where it expects `core-4`.
|
||||
|
||||
Give both prompts the team's label for each repo of the table where the table names it (`repo_pick.team_label`, `also`), and keep `repo:<name>` for a repo the table doesn't name. `finish.task` already knows each repo that lacks its review, so it can name each one's label outright, as `label_of(Repo(name), team)` gives it. The README states the pick's spelling (`repo-rule.md`'s bullet) but not the finding's, so it needs no change.
|
||||
|
||||
Touches:
|
||||
- `bin/do_epic/findings.py`: `LABELS`, `instructions` (small), `written` (small)
|
||||
- `bin/do_epic/finish.py`: `task` (small)
|
||||
- `bin/do_epic/test_findings.py`: `Instructions`
|
||||
- `bin/do_epic/test_finish.py`: `TheFinishingChunksTask`
|
||||
|
||||
### 446. Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.
|
||||
|
||||
Item 422 judges a worker that stalls before its result, but only reports: each verdict goes to the terminal and to `stuck-workers.md` in the project's transcript archive. Question for the human: after a few days of verdicts there, do they match what you would have done? Once you say yes, kill only the process a `stuck` verdict names, and only where the pid is below the worker's claude, never the worker or the loop, and record the call in a decision.
|
||||
|
||||
Reference in New Issue
Block a user