From adbebb38fd6a18bb751915e164c9299fa73061c1 Mon Sep 17 00:00:00 2001 From: sneak Date: Wed, 14 Oct 2026 05:39:31 +0000 Subject: [PATCH] TODO.md's Next Step names the open issues, not a closed one (closes #194) Next Step said the cache design, issue 36, waits on sneak's review. That issue closed on 2026-10-03. Next Step now names what is open: the backup concurrency issue, built in pull request 192 and waiting on review, and the live-account check that only sneak can run. Model: opus-5-5 --- TODO.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/TODO.md b/TODO.md index 5f555ea..c231724 100644 --- a/TODO.md +++ b/TODO.md @@ -17,14 +17,22 @@ pre-1.0 # Next Step -None: no implementation work is open. The cache design, -https://git.eeqj.de/sneak/quak/issues/36, waits on sneak's review. +`quak backup` downloading one original at a time, +https://git.eeqj.de/sneak/quak/issues/182, is fixed in +https://git.eeqj.de/sneak/quak/pulls/192, which waits on review. No other +implementation work is open. The check of quak against a live Ente account, +https://git.eeqj.de/sneak/quak/issues/187, needs an account only sneak has, so +it waits on him. Tagging and releases are decided by sneak alone, and happen only when he declares one. # Completed Steps +- 2026-10-14: Next Step said the cache design, issue 36, waits on sneak's + review, though that issue closed on 2026-10-03 (issue 194). It now names the + issues open on the tracker. + - 2026-10-14: A backup whose lock is lost no longer dies with a stack trace (issue 184). `lockBackupDirectory` gives proper-lockfile an `onCompromised` that records why the lock was lost instead of throwing from its timer, and -- 2.54.0