If you find a very critical bug in software on the day before its scheduled release date, how would you handle this situation?

Question

Anonymous · Accepted Answer

First, I will try to find the impact of the bug on the application-impacted user
groups and the number of users that would be impacted, as well as the impact on
the downstream system. If the bug will impact a small set of users or has no
downstream impact, I will document it as a known issue under an existing bug in
the backlog and proceed with the release. if it's a medium-severity bug that has
a manual intervention or roundabout, and I will still document the bug as a high
priority item for fixing in the next immediate release and move forward with the
release . If its more critical bug that impact more users with the manual
workaround then We will discuss with the team and make a choice to stop or
proceed with the release . If there is no work around then we will have to stop
the release irrespective of weather we a fix for the critical bug or not as the
fix in the last minute may introduce anther few set of bugs.

If you find a very critical bug in software on the day before its scheduled release date, how would you handle this situation?

Did you come across this question in an interview?

Answers