Suggestions on bug lifecycle and release management

Posted by Andrew Edgecombe on Stack Overflow See other posts from Stack Overflow or by Andrew Edgecombe
Published on 2010-04-21T01:14:37Z Indexed on 2010/04/21 1:23 UTC
Read the original article Hit count: 482

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?

© Stack Overflow or respective owner

Related posts about bug

Related posts about management