Matt, I'm sure your voice is heard, but Witango does not always respond directly. I can substantiate both of your experiences, and I'm sure that the installer issue with the missing DLLs will be fixed in the next release. I also have the same issue with CRLF formatting/encoding in the DirectDBMS box, although I haven't brought this up to Witango because I usually don't debug the studio.
Let me add, for everyone reading... Sending bug reports, feature requests, etc. to [EMAIL PROTECTED] is fine, however, there is a bug reporting tool at developer.witango.com (under utilities) which is preferred. In some cases you might not be the first one reporting a bug, and in most cases (unless an engineer needs more information about the bug) they won't respond. If you would like to hear back, state so in the email or the bug report. Also, you should post your experience to the list. Perhaps someone else has had the same (but hasn't said anything), perhaps there's an update or work-around. I will personally look into almost any server runtime bug that I hear about, as I'm very interested in getting the server to run as solid as possible. Also, every should note that most bugs, once properly reported, isolated and understood can take weeks, usually a few months, before a public release will contain a fix. The reporting and isolation time can add significantly to this. This has nothing to do with the staff of WT, or the programming time needed to actually fix a bug, but more to do with the general production schedule of software and QA testing (which WT does a lot of). If there is a significant bug in the server which is preventing you from running your website, email [EMAIL PROTECTED] or [EMAIL PROTECTED] and inquire about any possible beta builds which might help. You should only do this if you feel comfortable running a beta (breaking B to fix A) and if the beta is actually going to improve your site's uptime. FYI- I currently know of no show stopper bugs in the server, so I doubt this would be the case. Lastly, I can answer: YES [EMAIL PROTECTED] is read. YES [EMAIL PROTECTED] does go to Phil. YES these people are busy with both 5.5 updates and 6.0 in the works. YES Phil and the engineers do read the list. YES they get the bugs that are reported and try to duplicate them in house. NO that's not always easy. Robert -----Original Message----- From: Matt Muro [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 5:33 PM To: [email protected] Subject: Witango-Talk: response from developer.witango or [EMAIL PROTECTED] Has anyone had success (heard back from Witango) when submitting bugs through developer.witango.com or writing [EMAIL PROTECTED] I submitted some problems I had installing W5.5.009 on Windows2003/Apache2.54 (Win32) but haven't heard back from anyone. Problems similar to those people have mentioned here about files in the wrong directories for W55 under IIS. Some changes to the clients.ini file and using an old .so module did the trick FWIW. I also wrote [EMAIL PROTECTED] about a problem with the DEV Studio 5.5.008 but no response from them either. Is anyone else seeing this DEV Studio problem under W2003? --> I open a DirectDBMS window to edit my SQL then close the window. When I open the window a second time all hard returns are lost and my SQL is on one line, making it next to impossible to make further edits :) I know Phil will write me back pretty quickly, but I hate to bother him and really want to get the developer.witango.com site used more so it becomes a better resource for us all. ________________________________________________________ Matt Muro [EMAIL PROTECTED] Harvard University phone: 617.998.8522 Division of Continuing Education fax: 617.495.9176 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
