Establish routine for releasing packages
Registered by
Christian Theune
We need to find a good point in time when to cut a new release for a package for which fixed bugs where registered (or changes have been made). The routine should make clear the responsibilities of developers, points in time for releases as well as expectations about the release making itself. It probably needs to involve some automation for alerting developers that releases are needed.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)