diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index ec7623c5..14df27ee 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -908,3 +908,8 @@ Where two preparers disagreed, the chosen one is named. H-A-170 sharpened: the indexer writes `release..` only for a mover that released a version in that pipeline, and on `pipeline-wanted` of a newer pipeline it frees the record of a module below that pipeline's revision only where the newer revision itself holds `release..`. P2, P7. +- **H-A-174 (a tier-late pipeline-wanted frees nothing, 18:00)** Met in the review of H-A-173: a tier-late + pipeline's later-tier movers released a version, so the newer revision holds their release record, yet their wants + were not written; freeing their older release on the tier-late event would remove the revision their want names. + A `pipeline-wanted` with outcome tier-late frees nothing; the same pipeline's later `pipeline-wanted` with outcome + running frees as H-A-173 says. P2, P7.