Not the most fun activity, but at the same time, serious Software Engineers usually take pride in what they do and are embarrassed about handing off defective software. The quarterly time pressures in a corporation are typically what gets them to compromise on quality.
Care to explain why OSS projects frequently have long lists of unpatched bugs if your point was even remotely close to accurate?
Likely because they're doing it in their spare time, so the project moves much more slowly. My point was that with open source projects, you see them starting at very low version numbers and it'll take them a very long time to reach 1.0. By the time they reach 1.0, the quality might be something like a 1.4.7 release of a commercial product.