What do we do when there is a known bug at the time of software release?

Questions by appravi

Showing Answers 1 - 8 of 8 Answers

bugger

  • Jun 21st, 2006
 

mention that in the release notes!

  Was this answer useful?  Yes

Bikramjeet Singh

  • Jul 7th, 2006
 

If there is any open bug at the time of release we mention in the release note which we send with the release, in open list of issues. As we know if client finds that we have mentioned the issue in relese note he will not be worried about the type of testing being done on the application. But if he himself finds that bug it will hurt our company image.  

If i find a defect at the time of software release, I will first escelate the defect to the Higher level Management, and based on their decession, i will raise the bug and High level management will mention it as a KNOWN issue in the Release Note or High level management might extent the project release date by consulting the client and fix the defect before release.

What do I do when there is a known bug at the time of a software release?

1) Verify the issue is clearly and completely documented and labeled as a known bug in our defect tracking system.

2) Ensure those who make business decisions based on knowledge of this bug actually know about the bug.  These persons may include Project Manager, Test Manager, Business Analyst, and Client Representative.

3) Make sure this known issue is clearly documented in Release Notes.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions