Persist Sprint state to DB
- Dominant language
- Elixir
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
I'm thinking we could do something fairly lightweight, such as serializing the sprint to DB after every change, and then reading it back if the process is restarted for an upgrade or what have you (the main goal being to avoid destroying all sprints every time we release a new version).
The data model could be as simple as a single `sprints` table with `id INTEGER`, `sprint_id VARCHAR(32)`, `sprint_name VARCHAR(255)`, and `sprint_data JSONB` fields.
Related: http://www.ubazu.com/restore-process-state-in-elxir
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is named. First trace how sprints are created and changed, then review the proposed sprints table and serialization approach. Done means existing sprints survive a process restart or upgrade and changes are persisted without losing state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100