Version service in poppy
Registered by
Obulapathi
The idea behind the blueprint is to version services. This allows the poppy providers to run analytics on poppy services to gather useful information like: What is the typical life of a poppy service, what are users updating (ttsl, restrictions, domains, origins ..), how are they updating (frequency of updates, in small batches or large patches ..), what are the common errors. This also allows poppy providers to perform postmortems when problems occur (individual service level or poppy level). An additional step in this direction would be adding scripts for the above mentioned use cases.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Obulapathi
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for future
- Implementation:
- Unknown
- Milestone target:
- next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)