Depending upon the severity of bug , 
if it is low i will release it as alpha version 
if it is high i will ask the client some time

Meeting the deadlines and releasing the product is very 
important. One has to take a call on the bug, based on the 
severity. 

If it is a show-stopper bug, it needs to be fixed at any 
cost, otherwise the bug is medium or less than that a patch 
of fixes can be provided after the release.

But the most important thing is to mention that in know 
issues in the release notes.

Meeting the deadlines and releasing the product is very 
important.

Along the product we will release notes, nothing but a 
document explains about the product and  list of known 
issues. issues.

It depends on the severity of the bug 

It's like show stooper we have to sole it and release by 
intemating to clients 
If it is low are medium by intemating to clint we can 
release by showing the around the neck

We do analyze the impact of the defect. The defect is 
logged in the defect Tracking System.

Include the same in the agenda of Release Management 
meeting. Take a "go" / "nogo" decision with all the 
relevant stakeholders in loop, (Project Manager, Product 
Manager, Customer etc..)

In Case of "Go" decision the defect is recorded under Known 
Issue List of the Release Note and the Product / 
Application is released.

In Case a no go decision the release quest is turned back 
with a note on the defect identified, and MOM on No Go 
decision.