TODO.md's Next Step names the open issues, not a closed one (closes #194)
check / check (push) Canceled after 0s

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
This commit was merged in pull request #195.
This commit is contained in:
2026-10-14 08:07:48 +02:00
parent e8e8e00887
commit 22ee2db479
+10 -2
View File
@@ -17,14 +17,22 @@ pre-1.0
# Next Step # Next Step
None: no implementation work is open. The cache design, `quak backup` downloading one original at a time,
https://git.eeqj.de/sneak/quak/issues/36, waits on sneak's review. 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 Tagging and releases are decided by sneak alone, and happen only when he
declares one. declares one.
# Completed Steps # 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 - 2026-10-14: A backup whose lock is lost no longer dies with a stack trace
(issue 184). `lockBackupDirectory` gives proper-lockfile an `onCompromised` (issue 184). `lockBackupDirectory` gives proper-lockfile an `onCompromised`
that records why the lock was lost instead of throwing from its timer, and that records why the lock was lost instead of throwing from its timer, and