Development record
2026-10-23 — Release hold, Q1 (facilitator on delegation, abcd-ae ruling 2026-10-23; supersedes the amended 2A trigger): a release counts as ended only when the reservation holder runs --release (including after a same-person --take-over) or when the release tag is seen on origin. A lapsed lease is reported on peers and in launch, never acted on. The tag sweep still runs from any copy whose holder equals the reservation's Abcd-Holder. Grounds: with lapse-as-ended, three round-1 reviewers reproduced the cutter's own next act re-arming withdrawn merges mid-cut, because nothing renews a release lease.
decisiondcn-2610230328220298
2026-10-23 — Release hold, Q1 (facilitator on delegation, abcd-ae ruling 2026-10-23; supersedes the amended 2A trigger): a release counts as ended only when the reservation holder runs --release (including after a same-person --take-over) or when the release tag is seen on origin. A lapsed lease is reported on peers and in launch, never acted on. The tag sweep still runs from any copy whose holder equals the reservation's Abcd-Holder. Grounds: with lapse-as-ended, three round-1 reviewers reproduced the cutter's own next act re-arming withdrawn merges mid-cut, because nothing renews a release lease.
Frontmatter
| id | dcn-2610230328220298 |
|---|---|
| type | decision |
| date | 2026-10-23 |
.abcd/work/decisions/dcn-2610230328220298-release-hold-q1-facilitator-on.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26102305214884022026-10-23 — Release hold, reading of Q1 (facilitator on delegation, iss-2610222014550692 round 3; reads dcn-2610230328220298): after the tag, or any tombstone, each withdrawal is re-armed by a copy of the person who recorded it (its By, the holder of the reservation commit that first recorded it, as the branch's history and the forge's record of pushes show), not by the reservation's current Abcd-Holder. Grounds: under the letter of Q1, another person's take-over followed by their --release would leave the first holder's withdrawals with nobody able to re-arm them, since a re-arm runs under the re-armer's own GitHub account and only the withdrawer's own copies re-arm. The tag sweep's every-act scope is unchanged.
- dcn-26102719263694252026-10-27 — Release hold, Q1 revised (facilitator on delegation, lane D on abcd-f5's ruling, 2026-10-27; supersedes Q1 of dcn-2610230328220298): a release reservation whose lease lapses with no release tag on origin ends its hold. The merges this cut recorded as withdrawn are re-armed, and only those, each with one comment on its pull request saying the cut lapsed. A merge the cut did not record is never armed. A cut that outlasts its lease renews it with abcd reserve rel-vX.Y.Z, so a live cut's withdrawals stay withdrawn. Grounds: on 2026-10-24 the person ruled that sessions do not hold merges for a lapsed release cut, which #1132 implements by naming a lapsed cut as holding no merge (iss-2610241104098581). That day two finished pull requests waited on rel-v0.15.2, a cut whose computer had crashed. Under the old Q1, merges such a cut withdrew stay withdrawn indefinitely, which contradicts that ruling. Q1's own risk, a cutter's next act re-arming merges mid-cut, is met by renewal: a cut that is still running is still renewing.