milestone.md: a close-only arm #218
No reviewers
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#218
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cadence/close-only-arm"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closing a milestone without opening the next one has been hand-written four times, most recently at the v3.5.4 close. Steps 4 and 5 both assumed the close opens a cycle, so "no cycle open" was a deviation from the workflow rather than a path through it.
Step 4 now asks which it is, with no preselected default, and carries the record form for
### Active. Step 5 gets its own close-only bullet. Step 6 already worked on both arms and is untouched.The arm lives inside step 4 rather than becoming a new step, so the ten external references to milestone.md steps 1, 2, 3, 4 and 7 all still resolve. weight-budgets.json moves in the same commit per D-17 (12183 -> 13307).
self-verify clean, prose-agreement 31/31.