-
(1845355) Order each status column by its entry stamp, and bump to 0.23.0
released this
2026-08-23 10:58:34 +00:00 | 70 commits to master since this releaseEvery view read its rows out of
collect_ticket_items, which sorts by
by_priority_then_titlebecause it sees one directory and no status. That
is the right order for the backlog, where priority is the clock. Past the
backlog the question changes: committed asks what has waited longest,
reviewing what was handed over first, done what just landed. All four
columns answering the first question is why a finished p5 sat above the p1
nobody had read yet.So each column takes its own order, through one
by_status_orderkeyed on
theStatusrather than four comparators at four call sites. Backlog
delegates to the comparator it already used. Committed sorts by
Committed Onascending and reviewing bySubmitted Onascending, so the
longest wait is at the head where the reader picks next from; done sorts by
Completed Ondescending, newest first, the way a changelog reads.
Ascending twice and once descending is one rule said three ways: the head of
every column is what the reader acts on next.A ticket carrying no stamp sinks below every stamped one in its column and
falls back to priority then title among its own kind, as do equal stamps --
mvwrites whole seconds, so a tie is real. A missing time is unknown, not
ancient, and unknown must not claim the head of a queue ahead of a wait
somebody can point at. Reading absence as the epoch would have come free
from the comparison and put every ticket filed before f460853 first.The comparison is a string comparison.
%Y-%m-%d %H:%M:%Sis lexicographic
in chronological order, the propertyDuealready relies on, so nothing
parses a date at sort time. The stamps are read on the pass
collect_ticket_itemsalready makes over each file, the rulecriteriaand
tagsalready hold, and never per comparison.Both
cmd_lsbranches,list_ids,columns_ofandcampaign::members
take it, which is why those loops walkStatus::ALLrather than
status_dirs(): the directory name does not say which stamp governs it. The
merge tab keeps priority then title outright and is pinned there -- it spans
statuses, so no single stamp governs it.cmd_tagsis left alone; it counts
into aBTreeMapand never reads an order.Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Downloads