Skip to content

Implement GFS retention policy and update related documentation - #253

Open
sir106 wants to merge 1 commit into
ttionya:feature/next-minor-releasefrom
sir106:feature/retention-policy
Open

Implement GFS retention policy and update related documentation#253
sir106 wants to merge 1 commit into
ttionya:feature/next-minor-releasefrom
sir106:feature/retention-policy

Conversation

@sir106

@sir106 sir106 commented Aug 21, 2026

Copy link
Copy Markdown

Implement a best-practice Grandfather-Father-Son (GFS) retention policy allowing flexible daily, weekly, monthly, yearly, and recent backup retention. Set all retention variables to 0 to keep all backup files (disable cleanup).

Comment thread scripts/includes.sh Outdated
Comment thread tests/units/env-priority/test.sh Outdated
Comment thread .env.example Outdated
Comment thread .gitignore Outdated
Comment thread Dockerfile Outdated
@ttionya

ttionya commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Thank you for your PR.

I fully agree that GFS retention policy should be added, and this feature has already been included in the plan for the next release #256 .

However, this PR includes changes that are not related to the GFS policy. You may either remove those unrelated changes, or close this PR and open a new one that contains only the GFS‑related functionality.

Please retarget your PR to the feature/next-minor-release branch after adjusting it.

@sir106
sir106 changed the base branch from master to feature/next-minor-release September 7, 2026 20:06
@sir106
sir106 force-pushed the feature/retention-policy branch from 53f1145 to 33ef029 Compare September 8, 2026 17:40
@sir106
sir106 force-pushed the feature/retention-policy branch from e4e370f to 2002b78 Compare September 9, 2026 21:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants