Design 47 H: H-A-173, a release pin only for a released mover, freed only by a newer release of it
This commit is contained in:
@@ -900,3 +900,11 @@ Where two preparers disagreed, the chosen one is named.
|
||||
a re-pin and was never built again against the release. H-A-167 holds for both forms: a module's fingerprint
|
||||
includes its sorted pins whatever form computed it, so every importer moves on a re-pin; a fingerprint with no pin
|
||||
stays as it was. P3, P5, P7.
|
||||
- **H-A-173 (a release pin only for a released mover, freed only by a newer release of the same module,
|
||||
17:55)** Met in the review of H-A-170: a passed pipeline's movers include ones the assigner never takes
|
||||
(superseded movers, movers that released no version, a tier-late pipeline's later tiers), whose want stays the older
|
||||
release; freeing their older release on the newer pipeline's `pipeline-wanted` would remove the revision their want
|
||||
names (the entry-missing fault again), and a mover that releases nothing would pin a revision per pipeline for good.
|
||||
H-A-170 sharpened: the indexer writes `release.<branch>.<module>` 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.<branch>.<module>`. P2, P7.
|
||||
|
||||
Reference in New Issue
Block a user