Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

With my fellow engineers we are putting in place a release process in a team that formerly was made only of biologists. I am going to make a presentation to explain the process to them and explain what advantages it brings.

I am looking for one example of a project that failed or got into real trouble due to the lack of release process. Are you aware of any ?


migration rejected from Sep 30 '13 at 16:59

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as primarily opinion-based by gnat, GlenH7, MichaelT, thorsten müller, Dan Pichelman Sep 30 '13 at 16:59

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 3 down vote accepted

I can't quote you any widely known infamous failures, only stories from my own experience.

Back in the days, we were developing a Windows app, and we had no formal release process. Several times we had real trouble reproducing bugs which occurred regularly on a client machine, but never on most dev machines.

In some cases, this was due to different versions of the same system/environment libraries installed on different machines. In other cases, we couldn't track back which version of the code was actually running on the client machine in question.

Another issue was that often we couldn't tell easily to clients what features / bugfixes were released in which product version. We tried to keep track of these manually, but of course it was error-prone, and sometimes we had to make educated guesses. While I don't remember this having caused any concrete trouble with customers, it definitely felt bad.

In another company later, we already had a documented manual build process. Of course, as we were only humans, every now and then the guy who happened to create the actual build misunderstood or messed up something, like forgot to put a label on the actual version of the project in the SCM, or put the wrong label, or copied the wrong version of some file into the release package, etc. Needless to say, it caused us grief every time down the line.

In the end I decided to write a script to automate the release process. People only had to pass in a few parameters, and it did some parameter checking too. This drastically improved the quality of our builds, and soon producing releases became a non-issue, like it should be.


With some help from Google, I came across this release process error in the military's Early Warning System (to detect nuclear strikes by the USSR):

To test the warning system, false attack data was intermixed with data
from actual satellite observations, put on tape, and run through the
system.  On November 9 [1979], the test tape of this sort was accidentally
left mounted on a secondary backup computer.  This machine was left
connected to the system in use.  When the primary computer failed, a
backup computer was activated, which also failed.  Then the secondary
computer came into play, causing the alert.

The release process should of course have prevented fake data entering a release machine, even if that machine was a 2nd level backup.


Microsoft's DRM system for XP, "Genuine Advantage" broke down when they put preproduction software on their server.

...For the customers who failed validation from Friday afternoon through Saturday morning the experience was that features we refer to as ‘genuine-only' features were disabled. These features are Windows Aero, Windows ReadyBoost, Windows Defender (in this state Defender will scan and identify all threats it would ordinarily, but will only clean ones marked ‘severe') and Windows Update (in this state only ‘optional' updates are unavailable, all others can still be downloaded, including security updates). Also a desktop message appears in the lower right hand corner of the desktop area. The message reads ‘This copy of Windows is not genuine' and the message is persistent until a successful validation is performed and the message goes away...


Not the answer you're looking for? Browse other questions tagged or ask your own question.