>>>>Hi,
>>>>Should we tell the truth of our program bugs to our client? Or, we make a story/other excuses ?
>>>
>>>Put yourself in the clients shoes...The answer is obvious.
>>
>
>
>Hi Mark.
>
>>not always, as a client i would not liek to know about every little bug but definately i would like to know about the more serious ones, especially those that may cost money. most poeple will know that there is no reasonable way that any code will be bug free and will accept that from time to time may have to be done to fix these.
>
>Agreed. But then reasonable people will not be put off by giving a "release notes" which, amongst other things, will contain the "known bugs" as at that time.
>
>>if they do not know about the bug AND it does not effect then there is no reason to tell them about it and the upgrade should be put down as new features.
>
>Its not new features if its a bug fix. Its misrepresenting the truth but I admit I am guilty of the same iro releasing a fix but mixing it amongst new features upgrade :)
>
>The original poster asks a question which indicates he knows the software has bugs. I suggest that the client be informed of this upfront. I have seen many complaints on this forum that MS do not report known bugs in VFP upfront to us. Well, now we are in the "clients shoes" and we dont like it. Why? Becuase now we find the bugs the hard way.

I think that they should be made aware of major bugs, but if they are something that will be fixed tomorrow, i don't think that its worth the hit on your reputation.
Slán
~M

>
>Obviously this topic is a personal philosophy so I accept that there is perhaps no absolute right or wrong. I also accept there are pratical issues as well especially if the bugs are minor. Personally though, I will not release a program if I know of any significant bugs upfront vs. accepting there are probably bugs but not knowing what they are at release time.