Code release abstraction
- It would be helpful to have some sort of code release abstraction.
- Milestones are designed to represent a period of work. Often, teams are using a milestone to represent a bunch of issues that are targeted to be worked on within a "sprint" or an "iteration".
- For many teams, the code release is separate from the milestone. Many variations. Here are a few examples:
- Release on a pre-defined schedule/date, say, every quarter. Then all the issues up to then will be released together all at once in one big release. Different teams within that organization might have had multiple sprints, and thus, used multiple, separate GitLab milestones to manage their work up to then.
- Release per sprint: At the end of the sprint/iteration, a team releases all the code at once.
- Release when ready: Throughout the sprint, as code is ready, it is released to production. The release might even have different teams' of work together.
Edited by Victor Wu