Enterprise open source Toolkit

Story: Debian tipped for February release

• 
• 

Refreshing change

For my part I am sick to death of software companies releasing new versions *before* they are ready. I want to have confidence that when the company release the software, they have done their level best to ensure that it has no outstanding showstoppers.

If I am planning a big roll out, I want to do so with software that works. If it doesn't, I will either have to roll back (which might not even be possible) or re-release when the fixes come through, but either way it will cost a fortune. I would normally be testing the new load before rolling it out. I would be doing so with, of course, the new version. If it doesn't release, I can't start testing. If it does release and it isn't ready, I would hope to find the problems and so fail the testing. I would be happier to have the company step up and say, that it isn't ready and therefore postpone the tests, I might not find the problems until after rollout.

Just because a circle of marketeers wave a magic press release over the product, doesn't magically fix problems. If it isn't ready, it isn't ready.

If it takes longer than planned to get things squared up, just be happy that they have the guts to say so. Just because it has become normal to test supposedly production versions of a product on the customers doesn't make it good practice.

• 
• 

• 
• 
• 

Full Talkback thread