From aa56e9b9e7c5b05b099750c4d8b957b251dbdb28 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 21 Oct 2026 14:42:27 +0200 Subject: [PATCH] Playbook 07: the fixed scope and fixing what you open agree, a blocking issue still goes in --- 00-META/process/07-feature-branches.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/00-META/process/07-feature-branches.md b/00-META/process/07-feature-branches.md index 31993317..cdc22723 100644 --- a/00-META/process/07-feature-branches.md +++ b/00-META/process/07-feature-branches.md @@ -64,16 +64,17 @@ built, no milestone of another design starts: its issues stay `open`, and nobody lead who finds another design's milestone already in `fixing` asks its owner before starting its own. A small fix ([playbook 08](08-small-fixes.md)) and an issue that is in no design's milestones are not held by this rule. -**Scope is fixed at the prepare step.** An issue found during a feature goes to the next milestone or the next feature, -never into the running one, unless it blocks the running one. +**Scope is fixed at the prepare step.** An issue found during a feature never goes into the running milestone, unless it +blocks the running one: it is fixed in between or right after the delivery, as the next paragraph says, or goes to the +next milestone or the next feature. **An issue opened along the way is fixed by the session that opened it** (the operator, 2026-10-21): it is never only listed under "Opened along the way" and left. A small one (one repository, about an hour) is fixed in between, as a small fix ([playbook 08](08-small-fixes.md)) while the milestone waits on a check, an Approve or a delivery plan; the rest are fixed right after the milestone's delivery, before the next milestone starts, together on one branch where -they share a repository. Either way it stays out of the running milestone's branch and pull request, so the scope -above holds. Only an issue owned by another design's running milestone, or one that needs a decision or the -operator first, waits, and the report says which and why. Each report's line "Opened along the way" says for every +they share a repository. Either way it stays out of the running milestone's branch and pull request, unless it blocks +the running milestone, so the scope above holds. Only an issue in another design's milestones (one design is built at +a time), or one that needs a decision or the operator first, waits, and the report says which and why. Each report's line "Opened along the way" says for every issue whether it is being fixed in between, after the delivery, or waits, and on what. ## Step 0 — Prepare (the lead, larger model)