Suggestions on bug lifecycle and release management
- by Andrew Edgecombe
Our group is currently analysing our procedures for managing formal software releases and integrating with a bug lifecycle.
What bug lifecycle model do you use? And why?
For example assume a that formal releases are generated for QA once per week. At what point do you mark bugs as resolved?
When the developer has committed their changes?
When the changes have been reviewed and merged into the release branch?
When the formal release candidate has been created?
And what process, or features of your bug tracking sofware, do you use for tracking this?
Are there any tips/suggestions/recommendations that you can share?