Linked by Eugenia Loli-Queru on Fri 27th Apr 2007 18:46 UTC
Thread beginning with comment 234612
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
You'll love this. The problem wasn't in the RCs. They made a change for the final release after the last RC that caused the issue. This is the QC issue I'm getting at, last minute changes blowing up the system.
I worked at a company that used to do this. We called it "Code and Burn". We would literally make code changes hours prior to releasing the gold CD. One time we totally killed someone's Windows NT machine. There wasn't much I could do about it. Some people have a higher tolerance for risk. I believe there should be a strict checklist for software releases. Any change to what is on the release, even comments, starts the release process again. Better to be late. There will still be bugs, but don't let it be because we short-circuited the release process.
Note: This is probably arm-chair quarterbacking at its best!





Member since:
2005-10-09
You'll love this. The problem wasn't in the RCs. They made a change for the final release after the last RC that caused the issue. This is the QC issue I'm getting at, last minute changes blowing up the system.