'Life of a bug'-questions #32
Description
@yveskerwyn you would add a section 'Life of a bug' which explains how the process for a bug would be from creation to closing it down.
Some questions I have slumbering around that:
- Should the BAM discuss all open issues? Maybe only all new incoming bugs. If the BAM discusses all open issues, it is basically a bug triage meeting and it violates the concept of having to look only once at a bug.
- Who and when is decided that a bug should become a task as the bug might require some investigation time to find the root cause and add a meaningful estimate. Should the estimate be done before adding it to the storycard?
- If a bug is found in a release which is GA, what should be the milestone for the bug. At OVS every commit gets packaged and promoted. Giving a new milestone name for every promote would be cumbersome, while adding them to a milestone (f.e. Eugene) which is already closed feels also weird.