durhamlass
New member
I really am struggling to see what all the fuss is about personally. Perhaps someone can explain carefully exactly what I am not seeing?
As am I. As a C++ software developer/publisher myself, I can tell you it is extremely difficult to work to a specific release deadline.
To hit the release date, there can be no last minutes surprises, and everything in the release candidate code has to work as expected when used under real conditions (which are not what even the best developers work under. That's why good testers are so valuable and so expensive).
Even with the best developers, testers and most effective development practices (we use a form of agile we've developed over the past 4 years) this is a very tricky proposition to say the least.
This particular bug sounds like a real edge case - the sort that Murphy's Law dictates you'll only find when it's most inconvenient and will take a fortnight to nail down and fix (memory problems are like that).
Hence I have some sympathy with Auran here. If you want a fixed release date, this is what usually happens. The alternative is no projected date and "we'll ship it when it's ready", which most markets won't accept.