CareerCup

I would first try to find out why the problem is there.
Once I understand the problem, I would try to see if there is any feasible solution.
If there is an easy solution that can be done in a day or two, I would have my team fix it and release a new build after testing.
If there is a hard solution that may take month(s), I would try to figure out what feature caused this issue. If I can identify a particular feature, I would revert that feature and release a new build to customer and later on work on to fix that Issue.
Lastly I would ask developers to be more careful in coding so that these things wont happen again.

Here is the step that I would follow:
1. I would have exactly the same configuration, hardware and OS wise as the customers.
2. I will be on the previous build that was before the update
3. I will work on the particular area that the users are complaining.
4. If I could not reproduce it on the previous build, I will update the build to the one with the users
5. I will try to repro the bug and see on what scenario it is creating the bug.
6. Will check if there is simple fix for it like from the configuration side. and if I can update to the prev build I will do that and see the impact of upgrade
7. I will notify the dev team what I have found, the steps that I user to repro.. so that it is easy for them to fix it
8. The feedback I would give to the developers is:
before rolling out a new code:
1. Make sure all the previous features are intact, or if there is a feature change make a brief note about it and let the users know that
2. Run the integration tests, unit tests and feature tests
3. After the update rollout, keep an eye on the users..

I would fire the people responsible and set the whole company on fire... any problems now??

first i will rollout the system to the previous version for user because we can not interrupt their work it may happen that it will take much time find the bug so first priority to provide them a previous version of system then .. i will take that latest version and try to find the bug and if found i will acknowledge dev team for re built the app(that software ) .

agreed with Arun Kumar Gupta .

Need to keep the setup in 2 different setups,
1 setup with previous image.
1 Setup with latest image(build) with logs enabled
Since the issue is not seen on the previous build, i will collect the logs on the latest build and share the same to developer as regression issue with High Severity.

Quick fix will be
1. Take feedback from the users when they face this issue(which application, which feature)
2. Run the same application and feature reported by user and see if it is reproachable, if yes, talk to dev team for quick fix and it will be qualified as a regression bug.

1. Try to find out what is the actual problem.
2. Try to reproduce that problem
3.Take a snapshot of a problem.
4.Discuss with team member about bug.
5.send snapshot & bug details to dev team.