Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP9.0 Bug List
Message
From
11/03/2005 03:33:31
Eyvind W. Axelsen
Profdoc Norge As
Oslo, Norway
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
00994044
Message ID:
00994740
Views:
14
Ken,

We appreciate your honesty on issues like these.

Thanks,

Eyvind.


>Hi Russell (and Jim and all),
>
>Let me be very open and clear about this issue. The primary reason we do not publish the complete bug list for VFP is that if we did, it may impact the sales of VFP. While almost all the existing bugs we know about only impact only one customer who found it, there are enough small bugs like this that add up to make it appear there are many problems when in fact the product is super stable and most people never even experience any significant problems - and if they did we release a hotfix, service pack, whatever is needed.
>
>The second reason we don't release the list is that it would take a significant amount of time to do so since we would have to go through all our bugs and format them removing some comments since some parts of our comments in the bug we would want to expose and others we wouldn't (either confidential information, cursing, and other non-essential details). That effort would be significant, taking time away from other priorities we are working on. On the other side and we want to be more transparent as a company and disclose more and more information to developers. But at this time, sales of VFP are more important than releasing a VFP bug list.
>
>The VFP team could do release the entire bug list if we wanted to with the above sacrifices, but at this time we are choosing not to (it has nothing to do with a company policy). You may or may not agree with this rationalization, but I figure you may appreciate a very direct and honest response to this request rather than just a "no". Hope this at least clarifies our position on this.
Previous
Reply
Map
View

Click here to load this message in the networking platform