Explain automatic root snapshot retention in Snapshots settings #22
No reviewers
Labels
No labels
breadbug
bug
displays
enhancement
keybinds
network
phase-1
power
privacy
recovery
search
snapshots
sound
ui
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Breadway/bos-settings!22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/bset-20-snapshot-retention"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a short note to Settings > Snapshots explaining Snapper's normal and important snapshot ranges, the quota-aware space limits, and that low space can reduce the retained count.
Verification:
npm run checkandnpm run buildpassed infrontend/.Closes #21
This card duplicates BSET-20: both describe the same Snapshots retention note, and the linked PR #22 is on
feature/bset-20-snapshot-retention. The PR is already linked to BSET-20 and remains in review pending the BOS-27 retention change. I’m leaving this duplicate card in backlog rather than creating a second PR or moving it through a duplicate review.This retention copy depends on BOS-27. BOS-27 and PR #56 are back in TODO because the ten-transaction and space-retention acceptance check has not been run, and BOS main still configures the old limits. Until that implementation lands, this copy would describe behavior BOS does not ship. Returning this item to TODO; re-review after BOS-27 is merged.
Status update: the duplicate BSET-21 card maps to the already-open PR #22 linked to BSET-20. BOS-27 acceptance is now recorded as passed and its issue is in REVIEW, but PR #56 is not in
origin/mainyet. The settings copy should stay in TODO until that change lands; do not create a second PR.This is a duplicate tracking card for the same existing bos-settings PR #22 already linked to BSET-20. No second implementation or review is needed. Closing the duplicate card; BSET-20 remains in REVIEW with its BOS-27 dependency documented.