Skip to content

🧹 Clean-Up File Versions #1419

@tbsbdr

Description

@tbsbdr

Description

User Stories

  • As a user I want old file versions to be cleaned up so that the quota is used efficiently while still keeping important versions available.

Value

  • save storage space

Acceptance Criteria

  • 50% rule Versions must never use more than 50% of the user’s storage quota. If the stored versions exceed this limit, the oldest file versions get deleted until it meets the disk space limit again.
  • Default versions clean-up pattern
    1. Last second one version is kept
    2. Last 10 seconds one version is kept every 2 seconds
    3. Last minute one version is kept every 10 seconds
    4. Last hour one version is kept every minute
    5. Last 24 hours one version is kept every hour
    6. Last 30 days one version is kept every day
    7. Older than 30 days one version is kept every week
  • Config: The default cleanup-pattern can be changed via config
    • auto Default, default clean-up pattern applies
    • D, auto Keeps versions at least for D days, apply default clean-up pattern to all versions that are older than D days
    • auto, D Delete all versions that are older than D days automatically, delete other versions according to expiration rules
    • D1, D2 Keep versions for at least D1 days and delete when they exceed D2 days.
    • disabled Disable version retention; no files will be deleted.

Definition of ready

  • Everybody needs to understand the value written in the user story
  • Acceptance criteria have to be defined
  • All dependencies of the user story need to be identified
  • Feature should be seen from an end user perspective
  • Story has to be estimated
  • Story points need to be less than 20

Definition of done

  • Functional requirements
    • Functionality described in the user story works
    • Acceptance criteria are fulfilled
  • Quality
    • Code review happened
    • CI is green (that includes new and existing automated tests)
    • Critical code received unit tests by the developer
  • Non-functional requirements
    • No sonar cloud issues
  • Configuration changes
    • The next branch of the OpenCloud charts is compatible

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    No status
    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions