Playbook 04 and design 47: the milestone is one release, not a feature step (review of #401)
mesh/merge-gate head 4872ccdb6b3b merged into trunk 0f63a73def93 — fail: head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-M…
mesh/repo-check head 4872ccdb6b3b merged into trunk 0f63a73def93 — fail: head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-M…
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate head 4872ccdb6b3b merged into trunk 0f63a73def93 — fail: head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-M…
mesh/repo-check head 4872ccdb6b3b merged into trunk 0f63a73def93 — fail: head 4872ccdb6b3b does not merge cleanly into trunk 0f63a73def93: in conflict 00-M…
mesh/delivery superseded: a newer head of the same pull request
This commit is contained in:
@@ -44,8 +44,8 @@ A design becomes **milestones**, and each milestone becomes **issues**:
|
||||
entry in the design.
|
||||
7. **Flip the status.** `status: in-progress`, `updated:` today; the design change goes through playbook
|
||||
[08](08-small-fixes.md) (one hq pull request).
|
||||
8. **Hand each milestone to playbook 07, one at a time.** The milestone is the feature step; its issues are the
|
||||
step's issues; the next milestone starts when the previous one's delivery plan is done.
|
||||
8. **Hand each milestone to playbook 07, one at a time.** The milestone is one release of playbook 07; its issues
|
||||
are the release's issues; the next milestone starts when the previous one's delivery plan is done.
|
||||
9. **On completion of the last milestone**, run the "when something ships" section of playbook
|
||||
[02](02-graduation.md).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user