TimeTraveller v1.3.0
First public test build since v1.1.1 — bundles three releases (v1.1.2, v1.2.0, v1.3.0). Thanks for helping test!
What's new since v1.1.1
Archive management (v1.2.0)
- Delete from the GUI. Right-click a cycle or a backup in the Archives tab → Delete cycle… / Delete backup….
- Type-to-confirm safety gate. The dialog shows the blast radius (shard files, bytes freed, dependent incrementals) and you must type the target's identifier; the Delete button stays disabled until it matches. The newest complete backup and incremental-bearing fulls are flagged.
- Reindex / Recover are now also in that right-click menu (previously easy-to-miss buttons).
- New CLI:
--delete-cycle CYCLE_ID,--delete-set GROUP_ID(refuse the newest complete backup / dependent fulls unless--force).
Self-describing archives & export (v1.3.0)
- Each shard now writes a
<archive>.meta.jsonsidecar (no extra read of the archive — the single-read write path is preserved). - Manifest rebuild:
--list-archives --refresh-from-mountreconstructs a lost on-mount manifest from the.meta.jsonsidecars. - Export bundle: right-click → Export cycle… / Export backup… (or
--export-cycle/--export-set --into DIR) copies a whole logical backup + all sidecars + a manifest slice, group-atomically (won't write a partial set).
Sharding control (v1.1.2)
- The plan editor now has a Parallelism control to set write-stream count (Auto / explicit).
Install
```
sudo apt install ./timetraveller_1.3.0_all.deb
```
(Architecture: all, pure-Python; needs python3 + PyQt6 + zstd.)
What I'd love feedback on
- The delete flow — is the type-to-confirm clear and not annoying?
- Discoverability of the right-click menu (delete/export/reindex/recover).
- Export → copy to another machine/removable → does it browse/restore there?
⚠️ Testing caution
Delete is permanent. Please test destructive actions against scratch/throwaway backups first, not your only copy of anything important.